Interactive tool
Which agent fits your work?
- Copilot fitsYou want suggestions while you type, or a chat pinned to the file open in VS Code or a JetBrains IDE.
- doki fitsAn agent is already editing the repo on its own and has stopped to ask a question. That agent is not Copilot.
| GitHub Copilot | doki | |
|---|---|---|
| Where it shows up | Inside the editor | Mac app, iPhone, Android |
| Suggests the next line | Yes | No |
| Steers a Claude or Codex session | No | Yes |
| Steers Copilot chat | That is Copilot itself | No. doki does not control Copilot |
| Several agents in parallel | Each chat in its IDE | One Inbox for the agents it supports |
| Subscription | GitHub | doki, separate from the models |
What Copilot solves
Copilot sits in the moment of typing: it completes, explains the open file, and proposes a change you accept in the editor’s diff. You still hold the keyboard most of the time.
That is a different pace from a terminal agent, which can spend minutes editing and running tests before it comes back with a question. Mixing the two paces is what makes it feel like you must pick one brand and drop the other.
What doki does not do with Copilot
doki does not read Copilot chat, does not accept its suggestions, and does not list Copilot among supported agents. If your day is only Copilot inside VS Code, doki does not add an Inbox to that chat.
It does add an Inbox to the agents that run outside that chat. The Claude Code vs GitHub Copilot page compares those two products. doki enters when Claude, Codex, or Cursor is already in the repo and you want to attend to them without living in each window.
Using both without mixing them up
A clean split: Copilot while you edit by hand, and an autonomous agent for a task that can move on its own. When that agent asks, the answer leaves from doki’s Inbox. Copilot stays in the editor for the stretch you want to write yourself.
Guard’s rules, worktrees, and diff review apply to the agents doki steers, not to Copilot’s inline suggestions. Each layer has its own permission.
If you were looking for a Copilot replacement
doki does not complete code as you type. If that is the need, Copilot, Cursor, or the editor completion you already use is still the tool. Cursor is among the agents doki can steer; the detail is in Cursor vs doki.
If the need is that nobody sits waiting in a terminal, the product is the Inbox, not another autocomplete.
Frequently asked questions
Does doki control GitHub Copilot?
No. Copilot stays inside the editor. doki steers other agents: Claude Code, Codex, Cursor, Gemini CLI, Droid, OpenCode, Aider, and more.
Can I pay for only one?
Yes. They are different subscriptions for different jobs. Copilot does not include doki, and doki does not include Copilot.
Does doki run inside VS Code?
doki is a Mac app. It is not an extension that lives in Copilot’s panel.
What if I use Copilot and Claude Code together?
That is a reasonable split: Copilot in the editor, Claude in the terminal, doki so you hear when Claude asks. Each one keeps its own session.