Interactive simulation
How doki handles Gemini CLI
Inbox0Waiting for the agent…
Which layout do you want for pricing?
Click an option or press 1, 2, or 3
- 1Finds the sessionDetects it by process: CPU and the terminal it runs in.
- 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 Gemini’s terminal
- Gemini CLI aloneOne visible session, and the rest of the day no other agent is asking questions.
- With dokiGemini shares the machine with Claude, Codex, or Cursor and you want a single list of who needs you.
| Gemini CLI | doki | |
|---|---|---|
| Writes in the repo | Yes | No |
| How doki finds it | — | By the process and its terminal |
| Real-time hooks | Does not use Claude’s | Status comes from the live process |
| Replying | In its terminal | doki types into that terminal |
| Same Inbox as Claude | No | Yes |
| Model account | Still Google’s |
Detection by process, not by folder
Claude Code and Codex leave sessions on disk, and doki reads them even after the window closes. Gemini CLI arrives another way: doki sees the process, which terminal it is in, and how much CPU it uses. If that terminal is still open, the reply is typed there.
That matches how Gemini is actually used, usually in a tab next to other CLIs. No config file is required to add it. It shows up when it is running.
Gemini next to Claude or Codex
It is reasonable to give two models the same task and keep the better diff, or to split the work: Gemini exploring, Claude implementing. Without a shared list, the one that finishes first waits in silence.
The Inbox uses the same status for all of them. The several agents at once guide describes how to archive what no longer needs anything and answer only what is urgent. If you would rather talk than switch windows, there is the voice router.
What this combination does not promise
doki does not resume Gemini in the background the way it resumes Claude (claude -p --resume) or Codex (codex exec resume). With Gemini the path is the terminal where the process already is. If you closed that terminal, you open the agent again.
It also does not move your Gemini history to doki’s cloud. The process and the session stay on the machine where you started them, whether that is your Mac or a server over SSH.
Permissions and undo
When Gemini proposes a sensitive command, Guard can ask before it goes through: deleting outside the project, sudo, a force push, reading secrets, a migration. The explanation arrives on the Mac and in the iPhone notification.
Your reply waits about two seconds before it is sent. If you dictated too much, Esc cancels it and Gemini never receives that message.
Frequently asked questions
Does doki replace Gemini CLI?
No. Gemini is still the agent that edits. doki shows the session and types your reply into its terminal.
Do I need hooks like Claude Code?
No. Gemini is detected from the live process. Real-time hooks are specific to Claude Code.
Can I have Gemini and Claude in the same Inbox?
Yes. Each one keeps its own conversation. They share the list of what needs attention.
Does doki include a Google account?
No. Gemini usage is billed by Google. doki is the app that steers the session.