Interactive simulation
How doki handles OpenCode
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, here or on a server over SSH.
- 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 OpenCode’s TUI
- OpenCode aloneYou want an open agent, in one terminal, with the provider you already connected.
- OpenCode in the InboxThat session shares the day with others, or it runs on a server and you want it on your Mac or iPhone.
| OpenCode | doki | |
|---|---|---|
| Coding agent | Yes | No |
| Agent license | OpenCode’s own | doki’s app, separate |
| Detection | — | Process, CPU, and terminal |
| Reply | Its TUI | doki types into that terminal |
| On a VPS or Mac mini | You start it over SSH | It reaches the Inbox with no open ports |
| Model | Whichever provider you set | Unchanged |
Why people pick OpenCode
OpenCode is usually picked for control: the client is open, the model can be one you already pay for, and the session is not tied to a particular editor. That settles the choice of agent. It does not settle four of those agents asking questions in four places.
doki assumes the choice is already made. OpenCode appears when the process is alive, with the same status as a Claude session: working, needs you, done, or error.
OpenCode on another machine
It is common to leave agents running on a Mac mini or a VPS so they continue while the laptop sleeps. doki connects over SSH without you opening ports on that machine. If OpenCode runs inside tmux, you type to it live. If you need to reach it from another network, doki-bridge tries the local network first, then a direct link, and only if you allow it, the server relay.
The walkthrough is in agents on remote machines. The laptop’s Inbox shows the server session next to the local ones.
What you see in the Inbox
OpenCode’s question arrives like any other: text, options if there are any, and keyboard shortcuts. J and K move through the list, a number picks, E archives. The keyboard detail is in the Inbox.
You can pin the model for the conversation by provider, attach a screenshot, or dictate a note. OpenCode receives that in its terminal. doki does not translate its TUI into another product.
Honest limits
Because detection is by process, OpenCode disappears from the list when the process exits. There is no background resume equivalent to Claude’s or Codex’s. Leave it in a terminal or tmux session if you want to come back later.
doki also does not replace OpenCode’s docs or providers. If OpenCode is not installed, doki does not invent it.
Frequently asked questions
Is doki a fork of OpenCode?
No. OpenCode is an agent. doki is the Mac app that steers sessions from several agents, OpenCode included, while the process is running.
Do I configure OpenCode so doki can see it?
No. If the process is in a terminal on the Mac, or on a machine connected over SSH, it joins the list.
Can I answer it from an iPhone?
Yes. The phone shows the same Inbox. The OpenCode session stays on the machine where it runs.
Does my repo pass through doki’s server?
No. The server introduces machines to each other if you use the bridge. SSH traffic is end-to-end encrypted, and the relay is optional.