Privacy policy
The short version: the app collects nothing, and this website collects almost nothing.
The app
codehatch runs entirely on your Mac. It reads the session files that Claude Code and Codex already keep in your home folder, and the list of processes running on your Mac, so it can show your sessions and take you to them.
- Nothing it reads is sent anywhere. It has no account, no sign-in, no analytics and no crash reporting.
- Its only network use is for updates. About once a day it reads a short list of versions from this website, and when there is a newer one, it downloads it from GitHub. Neither sends information about you or your sessions, and you can turn the check off in settings.
- Its own settings, such as repos you chose to hide, are stored on your Mac.
- It keeps a small log of what it did, such as a session you clicked, for troubleshooting, in
~/Library/Logs/codehatch.log. It notes session names and folders, not your conversations or code, stays on your Mac, and is kept under 1 MB.
What it adds to your Mac
The first time it runs, codehatch offers to add two small pieces outside itself. It works best with both, and the welcome window says what each one is before anything is added. You can leave either out. The hooks can be turned off later in settings, and the helper removed from your editor’s Extensions list. Both are plain files you can read.
- Hooks, for live updates. Claude Code and Codex can run a small script when a session starts, stops or asks for something. Setting this up adds codehatch’s script to their settings files (
~/.claude/settings.jsonand~/.codex/hooks.json), after saving a copy of each. The script notes which session changed and when, in a file on your Mac. It does not keep your prompts or the replies. Turning the setting off removes it again. Without it, codehatch still works, but it notices changes several seconds late. - An editor helper, for Cursor and VS Code. A small extension that lets codehatch bring the right terminal tab to the front and reopen a closed session in the right project. It also writes small files on your Mac noting which terminal is in front, and which folders and terminals each editor window has, so codehatch brings back the right window. It makes no network connections. When codehatch updates, it updates the helper too. Without it, codehatch can bring your editor forward but cannot pick the tab. Terminal and iTerm2 need no helper.
What it asks macOS for
The first time you jump to a session in Terminal or iTerm2, macOS asks whether codehatch may control that app. Allowing it lets codehatch bring the right tab to the front and resume a closed session in a new tab. It uses this for nothing else. If you say no, your sessions still show in the list, and you can change your answer later in System Settings › Privacy & Security › Automation. Cursor and VS Code go through the editor helper instead, so they need no permission.
Apart from adding and removing its own hook entries, codehatch never writes to Claude Code’s or Codex’s files.
The source code is public, so you can check all of this yourself.
This website
- It counts visits with Vercel Web Analytics: which pages are opened, the referring site, and the country, browser and type of device. It uses no cookies, does not follow you to other sites, and keeps nothing that identifies you. There are no ads or other trackers.
- It loads nothing from other companies. Its fonts and images are served from this site.
- It is hosted by Vercel. Like any web host, Vercel’s servers briefly log requests, including IP address and browser type, to deliver the site and keep it secure.
- The app itself downloads from GitHub, and the GitHub and YouTube links take you to those sites. Each has its own privacy policy.
Changes and questions
If any of this changes, this page will be updated before the change ships. Questions can go to the project’s issue tracker on GitHub.
Last updated November 19, 2026.