Codonic
← All developer tools

hopsesh

Continue any coding-agent session, on any machine, in any agent

  • macOS
  • Windows
  • Linux (CLI)

Install the CLI · macOS and Linux

brew install roeehrl/tap/hopsesh

Free Version 0.7.0 · Open source, Apache-2.0 · Alpha · Not affiliated with Anthropic or OpenAI

The hopsesh macOS app listing seven Claude Code and Codex sessions from this Mac and the machine studio, grouped by repository, with Hop here and Continue in Codex here for the selected one.

Start on your desktop, pick up on your laptop, let the other agent take over or hand work to the cloud. hopsesh brings the session and the code, shows a preview before every move and can undo it.

Watch

See it in 34 seconds

Narrated, with captions. The machines, repositories and sessions are made up.

Inside the app

A look inside

  1. Every session of every agent, on every machine.

    Grouped by repository, with the agent, machine, branch, last prompt and whether it is running now.

    The hopsesh macOS app listing seven Claude Code and Codex sessions from this Mac and the machine studio, grouped by repository, with Hop here and Continue in Codex here for the selected one.
  2. Continue it in Codex, from the keyboard.

    The ⌘K palette (Ctrl+K on Windows) finds the session; Continue in Codex opens the plan.

    Made-up machines and sessions, recorded from the project’s own demo.

  3. See what carries over before anything moves.

    The loss report: what carries over, what changes for this machine and what is left out.

    The plan to continue Fix flaky checkout tests in Codex: 9 messages and 6 tool calls carried over, 5 paths mapped to this machine, 3 reasoning blocks left out as private to Claude Code, and the repository found here.
  4. Then pick up in the other agent.

    The command to continue, with the Codex session written and the Claude Code session kept.

    The result page: Fix flaky checkout tests continues in Codex on this Mac, with the codex resume command and what happened, the Claude Code session kept here too.
  5. Hand it to the cloud, and see what goes.

    The cloud gets an editable briefing, likely secrets masked, and a branch of your unpushed work.

    .env files and keys stay on this Mac.

    Handing Find the codeword to Claude Code cloud: what carries over, what changes and what stays here, the 721-token briefing, and the branch hopsesh pushes from this Mac.
  6. Cloud sessions beside your own.

    Claude Code cloud, Codex cloud and Copilot in one list, each with Bring to this Mac.

    Each cloud is off until you turn it on.

    The sessions list with a Claude Code cloud session, a finished Copilot cloud agent task with its pull request, Claude Code and Codex sessions on this Mac and a finished Codex cloud task, each with Bring or Resume.
  7. A terminal of its own.

    Resume a session in a tab.

    When Claude Code asks whether it trusts a folder, you answer, never hopsesh.

    The hopsesh Terminal docked below the sessions list, with a tab where Claude Code asks whether it trusts hopsesh’s hand-off folder and a second tab running a resumed session.
  8. Undo, on every machine it touched.

    Activity lists every move and continuation with its own Undo.

    The Activity page: one copy on studio waiting to be marked, and two continuations to Codex and one hop from studio, each with an Undo button.
  9. Every machine, and what it still needs.

    hopsesh’s mark shows whether each machine receives sessions; Up next lists what is left, with its fix.

    Receiving stays off until you turn it on.

    Settings › Machines: this Mac and studio all set and receiving sessions; laptop selected, on hopsesh 0.6.2, with Up next listing the update to 0.6.3 and receiving to turn on; nas reached over SSH only, without hopsesh.
  10. Each agent is a module.

    Claude Code and Codex today, each with its tested versions.

    A small SDK, so the next agent does not touch the core.

    The Agents tab of the hopsesh settings: Claude Code and Codex, each with its version, its capabilities and its own options.
  11. The same app on Windows.

    Windows 10 and 11, on x64 and Arm64: the same pages, with Ctrl+K for the palette.

    It installs per user, with no administrator rights.

    The hopsesh app on Windows, listing nine Claude Code and Codex sessions from this PC and the Linux machine studio, grouped by repository, with Fix flaky checkout tests selected and its repository cloned here at C:\Users\alice\src\webapp.
  12. It updates itself.

    Settings → Updates → Install and restart checks the release’s signature and checksum, installs it and reopens the app.

    The daily check for updates is your choice.

    The Updates tab of the hopsesh settings on Windows: a newer version available, with Install and restart, See what’s new and Check now, and the daily GitHub check turned on.

Built for the job

Who hopsesh is for

Coding agents on more than one machine

Desktop, laptop or a Linux box over SSH, even with different usernames and systems.

Moving work between Claude Code and Codex

Hand a session to the other agent or its cloud; bring it back intact.

People who keep it on their own machines

Sessions travel over your own SSH, with no account, no server and no telemetry.

Capabilities

What it does

Every session of every agent

Claude Code and Codex sessions from every machine you allowed, grouped by repository, with live state.

Hop it here

Finds or clones the repository, recreates the worktree, rewrites paths and blocks the copy left behind.

Continue in the other agent

Claude Code to Codex or back; going back adds only the new work to the original.

Hand it to the cloud

Claude Code and Codex clouds get a briefing and a branch; .env files and keys stay.

Undo on every machine

hopsesh undo reverses the newest move or continuation, on the other machines too.

CLI, terminal UI and an app

One engine behind all three; the app runs on macOS and Windows and updates itself.

Practical guides

Start with what you want to do

Claude Code

How to move a Claude Code session to another computer

7 minute read →
Codex

How to resume a Codex session on another machine

6 minute read →
Claude Code

Claude Code history gone after moving a project folder? How to get it back

6 minute read →
Claude Code and Codex

How to continue a Claude Code session in Codex (and back)

7 minute read →
Codex and Claude Code

How to continue a Codex session in Claude Code (and back)

6 minute read →
Claude Code on the web

How to hand a Claude Code session to the cloud and bring it back

6 minute read →
Comparison

hopsesh vs Claude Code Remote Control: drive the session or move it

7 minute read →
Claude Code and Codex

Hit Claude Code’s usage limit? Continue the session in Codex (and back)

5 minute read →
Claude Code

claude --resume says “No conversation found” after copying a session: the fix

5 minute read →
Claude Code and Codex

Where Claude Code and Codex store sessions (and how to move them)

4 minute read →
Claude Code

How to use Claude Code sessions on two computers (laptop and desktop)

5 minute read →
Claude Code and Codex

Moving to a new Mac or PC? How to bring your Claude Code and Codex sessions

5 minute read →
Claude Code

How to move a Claude Code session from Windows to Mac (or Mac to Windows)

5 minute read →
Claude Code

How to bring a Claude Code session from a remote server to your laptop (and back)

4 minute read →
Claude Code accounts

Claude Code with two accounts on one computer: switching and moving sessions

4 minute read →
Claude Code

How to export and import a Claude Code conversation

4 minute read →

Free and open source

Get hopsesh

Install the CLI Terminal macOS and Linux · Command line and terminal UI brew install roeehrl/tap/hopsesh Without Homebrew: curl -fsSL https://raw.githubusercontent.com/roeehrl/hopsesh/main/scripts/install.sh | sh, which checks the download against the release’s checksums and signature.
hopsesh for Mac .dmg macOS app · macOS 13 or later · Apple silicon and Intel · v0.7.0 Download Signed and notarized by BlueGuru LLC. Updates itself from Settings → Updates.
More ways to install
  • With Homebrew the same app, from the roeehrl tap brew install --cask roeehrl/tap/hopsesh-app
hopsesh for Windows .exe Windows app · Windows 10 or 11 · x64 · v0.7.0 Download Not code-signed yet: at SmartScreen, click More info, then Run anyway. Smart App Control, if on, blocks it.
More ways to install
  • Installer for Arm64 Windows 10 or 11 on Arm
  • Portable .zip x64 or Arm64, no install, on the release page
  • Command line with Scoop from the roeehrl bucket, without the app scoop bucket add roeehrl https://github.com/roeehrl/scoop-bucket; scoop install hopsesh
  • Command line only in PowerShell, without the app irm https://raw.githubusercontent.com/roeehrl/hopsesh/main/scripts/install.ps1 | iex
Linux packages and all files GitHub Latest release · .deb, .rpm and .apk for amd64 and arm64, a portable Windows app .zip, plus archives Open on GitHub Release notes, checksums and every build of the current version. Source on GitHub GitHub Apache-2.0 · Go 1.26 or later to build Open on GitHub From source: go install github.com/roeehrl/hopsesh/cmd/hopsesh@latest
Read the step-by-step setup guide

The short answers

Questions about hopsesh

Is hopsesh free?

Yes. hopsesh is free and open source under the Apache License 2.0.

Which coding agents does hopsesh support?

Claude Code and Codex. Each is a module behind a small SDK, so more agents can be added without touching the core.

What gets lost when a session continues in another agent?

The plan tells you before anything is written. Usually the conversation arrives as text, long outputs are shortened and the other vendor’s reasoning is left out. Bringing it back adds only the new work to the original, so nothing there is lost.

How is this different from Codex’s own import of Claude Code sessions?

Codex’s importer converts sessions on one machine. hopsesh can use it when you ask, and adds your other machines, the repository, a loss report, a briefing and a way back that keeps the original session intact.

Does anything leave my machines?

Between your machines, nothing: sessions go directly over SSH. No server, no telemetry, no Anthropic or OpenAI API calls. A cloud you turn on gets a briefing and a branch, not the conversation. The apps check GitHub for new versions only if you say yes.

Is there a Windows app?

Yes, for Windows 10 and 11 on x64 and Arm64. It installs per user, without administrator rights, and puts hopsesh on your PATH. It isn’t code-signed yet: at SmartScreen, click More info, then Run anyway. With Smart App Control on, Windows 11 blocks it.

How do I update hopsesh?

In the app, open Settings → Updates and choose Install and restart; it checks the signature and checksum first. On the command line, run hopsesh update, or brew upgrade or scoop update hopsesh if you installed it that way.

Do I need Tailscale?

No. Any machine you can ssh to works, including aliases, ProxyJump and ProxyCommand from your ~/.ssh/config. Tailscale just makes machines easy to find.

Does the other machine need hopsesh installed?

No. Bringing a session here needs only an SSH server there (Remote Login on macOS, OpenSSH on Windows). Sending one there needs hopsesh on that machine, with receiving turned on. Settings › Machines lists what each one still needs, with the fix.

What if the session is still running on the other machine?

By default, hopsesh copies it as it is and hands it off; later messages in the copy left behind stay there. With --fork, both copies continue. hopsesh won’t replace a session open on this machine unless you ask it to quit it first.

What if the two machines use different accounts?

The conversation stays. hopsesh asks each agent which account it is signed in to, and if they differ it leaves out what only the original account can use, such as Claude Code’s signed thinking blocks and Codex’s encrypted reasoning. It never reads Codex’s auth.json.

How is this different from claude --teleport or Remote Control?

hopsesh moves sessions between your machines, so they continue with the files and tools where you are. Teleport brings a Claude Code web session here; hopsesh runs it for you. Remote Control drives a session where it runs: hopsesh shows whether it reaches each running Claude Code session, turns it on for one in its terminal, and can start every session on a machine connected.

Can hopsesh hand a session to Claude Code on the web or Codex cloud?

Yes. It runs claude --cloud or codex cloud, signed in as you, with a briefing and a branch of unpushed work. Codex cloud works only with older environments for now. Copilot, Jules, Devin and Amp are experimental. Each cloud is off until you allow it.

What does a cloud get when I hand a session off?

A briefing hopsesh writes (never a model), with likely secrets masked, and a branch, both editable in the plan. Tool output and hidden reasoning stay; .env files, SSH keys, .pem and .key never go. The conversation goes on the branch only if you ask.

What happens to the session I moved away from?

It keeps its title and, by default, refuses new prompts until you move the session back, so the copies never drift apart. In Settings you can make it only warn or leave it alone, or lift the block for one session.

How do I undo a move?

hopsesh undo reverses the newest move or continuation, and hopsesh undo with a session id a specific one, on the other machines too. In the app, every move has an Undo in Activity.

Is hopsesh made by Anthropic or OpenAI?

No. hopsesh is an independent project, not affiliated with, endorsed by or sponsored by Anthropic or OpenAI. “Claude” and “Claude Code” are trademarks of Anthropic, PBC, and “Codex” and “OpenAI” are trademarks of OpenAI. They appear here only to say what hopsesh works with.

Privacy by design

What hopsesh knows about you

  • hopsesh collects nothing about you. No account, no analytics, no telemetry, no crash reporting.
  • There is no hopsesh server. Sessions move only between your own machines, over your own SSH, or to an agent’s cloud you turned on, through that vendor’s own command line.
  • hopsesh never calls the Anthropic or OpenAI API. Only Claude Code and Codex themselves talk to their models, under each machine’s own login.
  • The macOS and Windows apps check GitHub for new versions once a day, and only after you say yes.
Read the full hopsesh privacy policy