Doko Agent indexes your symbols, call sites and config, plans the change against the code that actually exists, and lands it as a diff you can read. Your test command is the referee, not the model's confidence.
of sessions end with your test and lint commands exiting clean
symbols indexed locally in 2.1 s, call sites included
in the median plan, each one readable before it runs
writes land in your working tree before you accept the diff
Scroll and the session moves sideways. Five stages, each one a thing you can open, read and undo — no black box between the prompt and the diff.
01 · read
Symbols, imports, call sites and config are indexed locally. Before it says “nothing else calls this”, it has looked.
index 41 files · 12.4k symbols
calls uploadRoute · 7 sites
config s3.client.tsband · ice · what it read
02 · plan
Six numbered steps, each naming the file it touches and the test that covers it. Disagree with step three and say so.
1 replace S3Client in upload.ts
2 move retry into lib/retry.ts
3 update upload.test.ts
4 run npm run checkband · violet · what it reasoned
03 · edit
Changes arrive as hunks on a branch, in your style, with the imports it added listed apart from the code.
+ import { putObject } from './s3'
- import { upload } from 'aws-sdk'
@@ routes/upload.ts · 3 hunksband · orchid · what matched your style
04 · check
It runs the test, lint and typecheck commands you named. A red exit is a red task, whatever the summary says.
$ npm run check
✓ 148 tests · 0 failing
✗ lint: unused importband · amber · what it held
05 · hand off
You get the branch, the plan it followed, the commands it ran and the one question it could not answer alone.
branch doko/upload-route
revert doko undo --session 8f21
open question: keep the legacy key?band · ice · what you can audit
Every step the agent takes is marked by where it came from: a file it read, a conclusion it reasoned, a convention it matched, or a gap it refused to fill.
Move the upload route off the legacy S3 client without breaking the signed-URL tests.
I read the route and its tests. Uploads are signed in s3.client.ts and consumed in routes/upload.ts1, so the client swap is local to those two files. Because the signed-URL helper is re-exported, the tests only need the mock path changed2. I kept the existing retry wrapper and your logger rather than introducing a new one3. The old upload keys remain valid for 30 days, so nothing in the bucket needs deleting yet4 — I cannot confirm that from the repo, so it is a question for you.
Point it at a checkout. It indexes symbols, call sites and config on your machine; nothing is uploaded to plan a change.
2.1 s indexThe task becomes numbered steps that name files and tests. You can edit, reorder or throw the plan away.
6 steps medianEdits land as hunks on a branch, in your formatting, with the imports it added called out separately.
branch · hunksIt runs the commands you named and reports their exit codes. A failing check sends it back to step two.
97.4% cleanSpecs, team process notes, and write-ups older than the framework. The agent reads all of it before it argues for a change — scroll and each document comes forward.
before any edit
Requirements, ADRs and the README are indexed alongside the functions. When the spec and the code disagree, that is a question for you, not a guess.
the team's habits
Lint rules, commit messages and review notes become constraints. The diff it writes already looks like the ones your team merges.
why the legacy path exists
Old write-ups and comments explain the odd branch in the upload route. It surfaces the reason before proposing to delete anything.
before it touches a system
Architecture notes and diagrams tell it what depends on the route being changed. A diff that looks local gets planned as the wider change it really is.
A session finishes when your own checks exit clean. Wire the agent into CI and a branch that fails them never reaches review.
$ doko run "migrate upload route" --gate
files read 41
steps 6
bands read 38 reasoned 11
style 4 held 1
npm run check · 148 tests · exit 0
ready for review
It is the first agent we let near a refactor on a Friday, because it showed us the plan before it wrote a line and reverted the whole session with one command.
Two days after we attached it, it had read every ADR in the repo and stopped proposing the pattern we retired last year.
Every plan has Doko Auto, effort levels, projects, file attachments, and your full chat history. Higher plans add messages, stronger models, pictures in the chat, and Doko Video: two short videos a month included, then any length or quality from a balance you top up.
$0a month
For trying Doko on real questions.
$16a month
For people who work with Doko every day.
$48a month
For long sessions and heavy reasoning.
Attach a checkout, name your test command, and watch the first plan arrive in under two seconds.