For people who run five, ten, twenty Claude Code terminals at once. See who is working and who is waiting on you, and answer Claude's questions in one click, without hunting through windows.
Every row in Peach is a real terminal running real claude. When a session waits on a permission or a choice, the question and its options come to you, and one click types the answer back into that terminal.
Unstaged screenshots from a working day. The interface follows your language; here it is in Hebrew.
Peach reads the session files Claude Code already writes, and the terminal screen. Nothing to configure, nothing to migrate. Drop back into the terminal whenever you like.
Every open session on one line: number, state, model, context size and the last thing it said.
Permission prompts and multiple-choice questions surface in Peach and are answered in the terminal that asked.
Every word of every conversation, including sessions closed months ago. 1.4 GB of logs in about 0.2 s, or ask in plain language.
Open any old session in a new terminal in one click, right where it stopped.
When the context window fills, one click writes a hand-off file and continues in a fresh session.
Paths in Claude's replies become chips and cards: Markdown rendered, images shown, PDFs drawn, editable in place.
What each sub-agent is doing right now and how long it has been running.
Hebrew, Arabic, Persian, Urdu and more, in the right order, even mixed with code.
No server, no account, no telemetry. The one model call, plain-language search, goes through your own claude.
No more copying paths into Finder. Every file Claude mentions becomes a card you can open, read and edit without leaving the conversation.
Put one filename between two right-to-left words and Terminal moves part of the line. Same characters in both boxes; only the rendering differs. Peach draws text with a complete Unicode bidi engine.
A 2 MB disk image, signed and notarised by Apple. Opens without warnings.
Universal binary: Apple silicon and Intel, macOS 12 or later.
Peach finds your running Claude Code sessions by itself. Keep working in the terminal as usual.
“I build with eight to ten Claude Code sessions open at once. The bottleneck stopped being the model. It was me, cmd-tabbing to find the one that had been waiting on a question for twenty minutes. Peach is the window I wanted.”
Neither. Every row is your real terminal running the real claude CLI. Peach reads the session files and the screen, and types your answers back into the same terminal.
No. The source isn't published; the GitHub repository holds the downloads, the release notes and the issue tracker. It is free, with nothing held back.
No server, no account, no telemetry. Plain-language search calls your own claude with Haiku; nothing of Peach's talks to the network.
No. Start sessions however you do now. Peach picks them up.
Not yet. Peach is a native macOS app. Open an issue if you want it elsewhere; it helps decide what comes next.