Privacy policy
hopsesh
For macOS, Linux and Windows
Last updated 10 October 2026
In short
- 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.
What hopsesh reads and moves
hopsesh connects only to the machines you allow, with your own ssh, keys and agent. Until you confirm a move it only reads: the session files of Claude Code and Codex on those machines, and the git state of the folders the sessions ran in.
When you move a session, or continue it in another agent, its files are copied from the other machine to the one you are on, rewritten for the new paths or converted into the other agent’s own format, and installed where that agent looks for them. They do not pass through us or anyone else.
To learn which account each agent is signed in to, hopsesh asks the agent itself: claude auth status for Claude Code, and Codex itself for Codex. It never reads Codex’s auth.json. Logins, keys, credentials, live sockets and account data are never copied; each machine and agent stays signed in on its own.
If you install the hopsesh skill, Claude Code and Codex can run hopsesh for you. They move a session only after you say yes, and the skill never handles passwords.
Sending sessions between your machines
Sending a session from one of your machines to another (hopsesh push) works only between your own machines, over your own SSH, and is off by default: a machine receives only after you turn on receiving there.
The receiving machine sees a read-only copy of that one session’s files and cannot read or run anything else on the sender. Nothing changes until you confirm, and undo on the sender reverses both machines.
Handing a session to an agent’s cloud
Each cloud is off until you allow it. When you hand a session to one, hopsesh runs that vendor’s own command line on your computer, signed in as you, and sends it two things: a briefing hopsesh writes, which you see and can edit first, and a git branch with the work you have not pushed. hopsesh masks likely secrets in the briefing; masking is best effort, and the plan shows what it masked.
The conversation itself, tool output and hidden reasoning stay on your computer. Credential-like files such as .env, SSH keys, .pem and .key files never go, whatever you pick. The conversation goes on the branch only if you ask, and then anyone who can see the branch can read it.
What the cloud session holds is kept by that vendor under its own terms, not by us. hopsesh never reads a vendor login and never calls a vendor’s servers itself.
What stays on your computer
Its settings, the machines you allowed and their SSH host keys, an undo journal and an audit log of every remote action are kept on your own computer, in hopsesh’s config and state folders. Removing those folders removes them.
Beside each session it moves, hopsesh writes a small file that records the session’s copies and hops, so the next move works from any of your machines. It travels with the session and stays on your machines.
For a machine that logs in with a password rather than a key, the password is kept in the macOS Keychain or Windows Credential Manager, or asked for each time. It is never written to hopsesh’s files or put on a command line.
A transcript can hold anything you pasted or a tool printed, secrets included. hopsesh scans for likely secrets while moving a session and can redact them from the copy. The scan runs on your own machine.
When hopsesh uses the internet
The macOS and Windows apps ask once whether they may check GitHub daily for new versions. If you say yes, the app asks GitHub which release is the newest and tells you when there is a newer one. If you say no, it never checks.
Installing an update downloads the release from GitHub and checks its signature and checksum before installing it, whether you choose Install and restart in the app’s Settings → Updates, run hopsesh update yourself or use the install scripts. The macOS app also checks the Apple developer and notarization.
Cloning a repository, or fetching the commit a session last saw, contacts wherever that repository is hosted, with your own git credentials, as if you had run git yourself. GitHub and other hosts see these requests as ordinary traffic under their own terms.
Your rights
Privacy law in the European Economic Area, the United Kingdom, California and elsewhere gives you rights over personal data a company holds about you: to see it, correct it, delete it, take it elsewhere, and object to its use. It also gives you the right to complain to your national data protection authority.
We hold no personal data about you through hopsesh, so there is nothing for us to hand over, correct or erase. What you create in the app stays under your control. We do not sell personal information.
If you have written to us by email, that correspondence is the one thing we do hold. Ask at dev@codonic.dev and we will delete it.
Changes to this policy
If this policy changes, the new version will be posted at this same address with a new “last updated” date above. The address does not change.
Contact
BlueGuru LLC — Codonic
dev@codonic.dev
Related: hopsesh · all privacy policies · support