Interactive simulation
How doki handles Claude Code
Inbox0Waiting for the agent…
Which layout do you want for pricing?
Click an option or press 1, 2, or 3
- 1Finds the sessionReads transcripts in ~/.claude/projects and, with hooks on, hears every change instantly.
- 2Tells youThe question rises to the Inbox with its options.
- 3You answerA key, your voice, or the iPhone. Two seconds to undo.
- 4Delivers the replydoki types into iTerm2 · or claude -p --resume
- Stay with Claude Code aloneOne session, you are looking at that terminal, and reading it there is enough.
- Add dokiSeveral Claude sessions, or other agents beside them, and you want to answer without hunting through windows. Also when you answer from an iPhone.
| Claude Code | doki | |
|---|---|---|
| Writes and edits the code | Yes | No. It delivers your reply to the agent |
| Where it lives | Terminal | macOS app, iPhone app, and an Android page |
| Several sessions at once | One window each | One Inbox with the status of each |
| How you hear about a change | You see it in that terminal | Real-time hooks, with a backup of the config |
| Replying | You type in that session | A key, your voice, or the same thread from the iPhone |
| If the terminal is closed | You reopen it | It can resume the session in the background |
| Dangerous permissions | The agent asks in its terminal | Guard explains the risk and you approve on Mac or iPhone |
| What you pay | Your Anthropic plan | A doki plan, separate from the model |
What Claude Code does
Claude Code runs in the terminal, inside the repository. It plans, reads files, edits, runs commands, and asks again when the next step depends on you: a layout, a push, a migration, a missing key.
Each conversation leaves a transcript on the Mac, under ~/.claude/projects. Three parallel tasks means three sessions. The one waiting on you stays quiet if that window is buried.
What doki does with those sessions
doki reads those transcripts and, if you turn on real time in Connections, adds its hooks to ~/.claude/settings.json. It keeps a backup first. After that it hears every change without you opening the window.
The reply goes out in two ways. If the session is in Terminal or iTerm2, doki types there. If it is not open, doki resumes it in the background with claude -p --resume. You keep starting the agent the way you already do.
- A status on every session: working, needs you, done, or error.
- Numbered options: press 1, 2, or 3 and the agent has its answer.
- About two seconds to undo a send with Esc.
- Files, screenshots, and transcribed voice notes on the same thread.
When it is worth running both
With a single Claude session and your attention already on that terminal, doki does not change the agent’s work. It starts to matter when a question is hidden behind another task, when Claude runs on a Mac mini or a server, or when you want to answer from your phone without an SSH client.
It also matters when Claude is not alone. A Codex reviewing the API and a Cursor session on the front end ask questions in different places. The Inbox collects them. The guide to several agents at once covers that case.
Limits worth knowing
doki does not pick Claude’s model and does not replace an Anthropic account. The code, the transcripts, and Guard’s rules stay on the Mac. doki’s server stores the account, the license, push tokens, and bridge machines.
You need macOS 26. Typing into some apps requires Accessibility; dictation requires the microphone and speech recognition. Claude hooks are optional: without them doki still discovers sessions from transcripts, with less immediacy.
Frequently asked questions
Does doki replace Claude Code?
No. Claude Code is still the one that reads the repo and writes the changes. doki finds the session, shows that it needs you, and delivers what you answer.
Do I have to start Claude differently?
No. You keep opening Claude Code as usual. doki detects the session that already exists and, if the terminal is not visible, can resume it in the background.
Do several Claude sessions show up together?
Yes. Each transcript is a conversation in the Inbox, with its own status. You can archive the ones that need nothing and answer only the ones that are asking.
Do the transcripts upload to doki’s cloud?
No. They stay on your Mac. The cloud account is for sign-in, the license, phone alerts, and the bridge to other machines.