codehatch

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.

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.

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

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.