The developer who runs the agent
Keeps the terminal, the code and the keys. Shares a link instead of a screen.
/covo-share · one commandWorks with
Claude Code
Codex Your Python agentPublic beta since October 2026The server runs no model and keeps no keyBuilt in Istanbul, used every day
Claude Code Codex Your Python agentPublic beta since October 2026The server runs no model and keeps no keyBuilt in Istanbul, used every dayHOW IT WORKSShare it once.
Share it once.
Work on it together.
Three steps take a session from your laptop to a team that follows it, talks about it and decides with you.
- 01
Share your session
In Claude Code, type /covo-share. Covo gives you a link for your team.
- 02
Watch and comment together
Your team sees each step of the agent as it occurs. Anyone can write a comment on a step.
- 03
Approve the risky steps
Before a risky command, Claude stops and asks for approval. One person on the team approves or rejects it.
Who it is forThree people, one session.
Three people, one session.
Each one gets something different.
The lead who has to say yes
Sees the risky call before it runs, approves it from the browser or the phone, with the diff beside it.
Approve · Reject · AutoThe teammate who was not there
Reads the thread, the plan and the changes later. Comments on a step. Forks the session on their own machine.
Catch up · ForkWe built Covo because the agent sessions in our team happened in one terminal, and the decisions in one head. Covo puts the session where the team is, and keeps the code where it was.
Ulaş Taylan, founder · Istanbul1.0 The mechanics · live in betaEverything your agent does.
Everything your agent does.
Seen, steered, shared.
A small set of tools that keeps your team next to the work instead of behind it.
One live timeline. Every step, the moment it happens.
Model calls, file reads, edits and commands appear for everyone the moment they happen. No screen share, no catch-up.
LIVEÇUCD4 watching
- Planning the changeclaude-opus
- Read payment.tscheckout/payment.ts
- Edit payment.ts+18 −6
- Run the test suite148 passed
A human approves the risky steps. Here, that is you.
Tool calls you choose wait for the controller: approve or reject it. Or set the session to Auto and Covo approves at once, like auto mode in your agent.
Approval neededWAITING
Bash · npm run migrate -- --env staging Try it. You are the controller.
1 waiting in your queue
Secrets stay secret. Masked before they leave.
API keys, tokens and passwords are masked on your machine, before anything is sent. Paste something below and see what your team would get.
or paste your own
2 secrets masked before it leaves
What your team seesDATABASE_URL=postgres://app:[removed]@db.internal/app STRIPE_KEY=[secret removed] DEBUG=trueRuns in your browser with the SDK’s rules. Nothing you type is sent.
Fork a session. Continue from any point.
Take a teammate’s session to your own computer and continue from any point, without touching theirs.
Çiğdem’s session Deniz’s fork, on his machine
Also: pass the controls · connect once · notes to the agent · usage at API pricesShow the four more
Pass the controls. One controller at a time.
One controller at a time keeps decisions clear. Hand over without losing context.
ÇÇiğdemAt the controls
UUlaşWatching
CCerenWatching
Çiğdem passed control to Ceren · context kept
Connect once. Share any session.
Install, pair the computer, and every Claude Code session on it can be shared with a link. Your team needs nothing but a browser.
$
Steer while it works. A note, not a restart.
Write a note to Claude Code or Codex from the browser. The agent reads it at its next step and changes course. Reject a call with a reason, and the agent reads why.
Claude Code Edit · src/db/config.tsrunning
Ceren Use the staging database here, not production.waiting for the next step
Claude Code Read Ceren’s note. I switch the connection to staging.
See what the agents cost. At API prices.
Insights → Usage shows the tokens of every session, by agent, person and model, and their value at API list prices. Covo gets the counts, never the prompts.
API value$41.20
Tokens18.4M
Requests2,310
Claude Code$28.40
Codex$12.80
Counts only. Covo never sees the prompts.
Inside the workspaceThis is the screen your team opens.
This is the screen your team opens.
Drawn here, real in the product.
The thread on the left, the plan and the changes on the right. Pink marks what is live or waits for a person.
Checkout service refactor Running 5:04Claude Code · claude-opus-5-5Share session
ÇiğdemGo ahead. Add the index too, and run the tests before touching the database.
editcheckout/payment.tswritecheckout/payment.test.tsrunnpm test · 148 passed
Claude CodeAll 148 tests pass. Next I add the index. That writes to the staging database, so I need an approval.
Approval needed to continue · Bash
$ npm run migrate -- --env stagingApproveReject
PLAN · 4 OF 6 DONE
@@ -38,6 +38,7 @@- const tax = computeTax(order);+ if (card.saved) return authorize(card, order.total);+ const risk = await fraud.score(order);
2.0 Your agent checks the work · new in 0.15Review, test, compare, measure.
Review, test, compare, measure.
With the agent you already pay for.
Four commands run your own Claude Code or Codex on your computer. The result goes to the session, where the team reads it. Covo runs no model.
$ covo reviewA review of the change
Your agent reads the session’s diff and writes a review with line comments. The team answers each comment in the session.
3 line comments2 actions before the merge
$ covo qaA QA check, 0 to 5
The agent applies the change in a throwaway copy, runs the linter and the tests, and gives a score.
tests pass no test added3.2 / 5
$ covo compare A BWhich fork did it better
Two forks of one task are done. Your agent reads what each one did and recommends one, with the reasons.
Recommended: fork B · 4.5fork A · 3.0
$ covo bench runClaude Code against Codex, on your work
Your merged pull requests become tasks. Each agent does them again from the commit before. Covo shows the time, the cost and a judged quality.
Claude CodeCodex
Your code stays on your machine. Only the report goes to Covo.
3.0 What stays whereYour agent stays home.
Your agent stays home.
Your team comes to it.
4.0 SecurityBuilt to be trusted
Built to be trusted
with your work.
A tool that sits next to your agent has to earn that place. Here is what we do with the little we keep about you, and with the session you share.
E-mail encrypted at rest
AES-256-GCM, found through a keyed blind index. A copy of the database does not reveal who you are.
Passwords never stored
Only a salted scrypt hash over a server-side pepper, at the cost OWASP recommends. Breached passwords are refused.
Confirmed addresses
No account exists until its address is confirmed. Every e-mailed link is single use and expires.
Secrets masked locally
Keys and tokens in the session are masked on your machine before anything is shared.
Sign out everywhere
See every browser, terminal and computer signed in, and end any of them, or all, in one click.
Leave whenever you like
Delete your account from your Account page. Your address and password are erased, not archived.
From our own sessionsWhat changed for us
What changed for us
after the first week.
“The first time Ceren approved a migration from her phone, we stopped doing screen shares.”
ÇÇiğdem, tech lead · Covo“I read the whole session on Monday morning instead of asking what happened on Friday.”
DDeniz, backend · Covo“Our keys never left the laptop. That was the sentence that got security to say yes.”
UUlaş, founder · Covo5.0 Public betaFree while we build it
Free while we build it
with you.
Every feature, for your whole team, while Covo is in beta. No card, no trial clock.
BETA$0for the whole team
- Unlimited shared sessions
- Claude Code, Codex and the Python SDK
- Approvals, hand-offs and forks
- Notes to the agent and usage at API prices
- Reviews, QA checks and benchmarks by your own agent
- Comments, briefs and notifications
- Your keys and code stay on your machine
6.0 FAQ
Questions, answered straight.
What is Covo?
A shared workspace for an AI agent session. You keep running Claude Code, Codex or your own Python agent the way you do today; Covo lets your team follow that session live, comment on it, approve the risky steps and take over the controls.
Does my code or my model key leave my machine?
No. The agent runs on your computer, with your files and your keys. Covo receives the session’s messages and steps (what the agent says and does), with secrets such as API keys masked before they are sent. It never needs your model key.
Which agents work today?
Claude Code (watch, comment and approve tool calls through its hooks), Codex sessions, and any Python agent through the Covo SDK, which also lets the team steer, pause and interrupt.
Does Covo run a model?
No. The server runs no model. The commands covo review, covo qa, covo compare and covo bench run your own Claude Code or Codex on your computer, with your subscription, and send only the report to Covo.
Do my teammates need an account?
To follow a session, no: they open the link and enter a name. To host sessions of their own, approve from their queue or get notifications, they create a free account.
How do you protect my account?
Your e-mail address is stored encrypted (AES-256-GCM) and looked up through a keyed index, so a copy of our database does not reveal it. Your password is never stored: only a salted scrypt hash over a server-side pepper. Every link we e-mail is single use and short-lived, and you can sign out everywhere or delete your account from your Account page.
Is it free?
Yes, while Covo is in public beta. No card is needed. If paid plans come later, we will tell you well before anything changes, and you will be able to export or delete your data.
What does “beta” mean here?
Covo is used every day, but it is young: some things will change, and we ship often. Tell us what gets in your way; the beta exists to find it.
Ceren Check the tax rule here.