Free while in beta · macOS and Windows
Every handoff,one thread.
Dococ keeps the markdown your frontend and backend hand each other in one place, shows whose turn it is, and opens Claude Code on it in the right repo.
Your Claude Code, your subscription. Dococ never sees your key.
Parcel
1 thread needs you.
Why Dococ exists
The reply was written. Nobody saw it.
Two files with the same name. One in Downloads, 181 lines. One in the backend repo, 284 lines. The extra 103 lines said the field had shipped three hours earlier and told mobile to delete a workaround. The copy mobile opened ended before any of that.
Sent over Slack, AirDrop, WhatsApp, or a commit to the wrong repo.
3–6
handoff documents per feature
~20
documents a day between one pair
0
systems tracking which asks shipped
How it works
From one Mac to the other, without a lost turn.
- Step 1
Claude writes the handoff
Write your md the way you already do. Dococ catches it three ways — a publish over MCP, a Claude Code hook, or a watch on your Desktop and Downloads — so nothing depends on remembering.
Publish over MCPClaude Code hookDesktop and Downloads watch - Step 2
It lands in their court
The document is read into a ledger of asks, each with its severity and effort, and placed on a shared board under whoever needs to act next.
- A-1Include tax lines in the order totalRelease
- A-2Round per line, not per orderHigh
- A-3Return taxBreakdown[] on /orders/:idFollow
- Step 3
They press Implement
Dococ opens a terminal in the right repo with Claude Code already pointed at the document. No hunting for the file.
Implement› claude "Implement docs/BACKEND-checkout-tax-2026-10-12.md"Reading the handoff · 5 asks, 2 block releaseA-1 Include tax lines in the order total … built - Step 4
The reply comes back on the thread
Answers, changed contracts and follow-ups land on the same thread. No ask reaches done until something has verified it.
- Include tax lines in the order totalverified
- Round per line, not per orderverified
- Return taxBreakdown[] on /orders/:idproposed
Autonomous mode
Or let Claude take the back-and-forth.
Turn it on for a thread and Claude works it turn after turn in its own git worktree. It never pushes. When the thread settles, you read the diff and verify.
- Runs in a separate git worktree
- Never pushes to your remote
- A person verifies before done
Turn 3 of the thread · Claude on both sides
- 01FrontendBackend
- 02BackendFrontend
- 03FrontendBackend
Privacy
Built so we couldn't snoop if we wanted to.
Your Claude, your key
Dococ never stores, forwards or proxies an Anthropic credential. The runner on your machine starts your own Claude Code with your own subscription.
We can't read your documents
Every document is encrypted on your machine before it leaves. Our server stores the ciphertext and only the routing details it needs — whose turn it is, each ask's status, timestamps — never what you wrote.
Plain files on your disk
Your handoffs stay where Claude wrote them: plain markdown in your repo. Uninstall Dococ tomorrow and every one of them still opens in your editor.
Never collected
- Claude Code transcripts
- Repo contents
- Repo paths
- Anthropic tokens
- Terminal output
In the app
Built for a ten-second glance.
The board
Every thread, sorted by whose court it's in.
Every ask, tracked
Did it ship? Severity, owner, evidence and status in one table.
- A-1Include tax lines in the order total
- A-2Round per line, not per order
Plain or Technical
Read a thread in plain words, or open the full contract.
Checkout totals now include tax. Backend put their half live this morning.
⌘K for everything
Jump to any thread, ask or document from the keyboard.
Finds loose mds
Handoffs left on your Desktop or in Downloads get gathered up.
BACKEND-push-tokens-2026-10-26.md
Nudge, don't chase
One click reminds the other side a turn is waiting.
FAQ
Questions, answered.
Nothing while it's in beta. Every team, project and agent, with no limits.
No. Dococ never stores, forwards or proxies an Anthropic credential. It starts the Claude Code you already use, signed in with your own subscription.
No. Documents are encrypted on your machine before they're sent. The server sees team and project names and the structure it needs to route turns, never what you wrote.
A Mac or a Windows PC, Claude Code, and the person on the other side of the feature. Dococ installs its small runner and one Claude Code hook during setup, after backing up your settings.
Yes. Dococ tracks turns between sides, so one person working frontend and backend gets the same board, ledger and Implement button.
They stay where they are. Dococ never moves your handoffs out of your repo; each one is a plain markdown file that opens in any editor.
Never ask “did you see the reply?” again.
Free while in beta. Download Dococ, sign up in the app, and invite the other side.
Sign-up happens inside the app.
