One agent session.
Your whole team, live.

Covo turns the coding agent on your machine into a shared workspace. Your team follows every step and approves the risky calls, while your code and keys stay with you.

In your coding agent

  • Free during the beta.
  • Set up in two minutes.
  • Keys never leave your machine.
Works with Claude Code Codex Cursor Your Python agent

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.

  1. Share your session.

    In your coding agent, type /covo-share. Covo gives you a link for your team.

  2. Watch and comment together.

    Your team sees each step of the agent as it occurs. Anyone can write a comment on a step.

  3. Approve the risky steps.

    Before a risky command, Claude stops and asks for approval. One person on the team approves or rejects it.

Three people, one session.

Each one gets something different.

The developer who runs the agent

Keeps the terminal, the code and the keys. Shares a link instead of a screen.

/covo-share · one command
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 · Auto
The 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 · Fork

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.

Model calls, file reads, edits and commands appear for everyone the moment they happen. No screen share, no catch-up.

LIVEÇUCD4 watching
  1. Planning the changeclaude-opus
  2. Read payment.tscheckout/payment.ts
  3. Edit payment.ts+18 −6
  4. Run the test suite148 passed

A human approves the risky steps.

Tool calls you choose wait for the controller: approve or reject it. Or set the session to Auto and Covo approves at once.

Approval neededWAITING
Bash · npm run migrate -- --env staging
Try it. You are the controller.
1 waiting in your queue

Secrets stay secret.

API keys, tokens and passwords are masked on your machine, before anything is sent. Paste something below and see what your team gets.

or paste your own
2 secrets masked before it leaves
What your team sees
DATABASE_URL=postgres://app:[removed]@db.internal/app
STRIPE_KEY=[secret removed]
DEBUG=true
Runs in your browser with the SDK’s rules. Nothing you type is sent.

Fork a session.

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

Pass the controls.

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.

Install, pair the computer, and every agent session on it can be shared with a link. Your team needs nothing but a browser.

zsh — ~/checkout
$

Steer while it works.

Write a note to the agent from the browser. The agent reads it at its next step and changes course.

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.

Insights → Usage shows the tokens of every session, by agent, person and model, at API list prices.

API value$41.20
Tokens18.4M
Requests2,310
Claude Code$24.60
Codex$10.90
Cursor$5.70

Counts only. Covo never sees the prompts.

This is the screen
your team opens.

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 staging
ApproveReject
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);

Review, test, compare, measure.

Four commands run your own coding agent on your computer. The result goes to the session, where the team reads it. Covo runs no model.

$ covo review

A 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 qa

A 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 B

Which 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 run

Your coding agents, 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.

quality ↑cost →Claude CodeCodexCursor

Your code stays on your machine. Only the report goes to Covo.

A building with three columns: your machine, Covo and your team

Your agent stays home.
Your team comes to it.

Your coding agent runs on your machine, with your code and your model keys. Covo mirrors the session, not the machine: messages, steps and results, with secrets masked on the way. Teammates follow live, comment and approve, and the decision goes back to your terminal.

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.

S.01

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.

S.02

Passwords never stored

Only a salted scrypt hash over a server-side pepper, at the cost OWASP recommends. Breached passwords are refused.

S.03

Confirmed addresses

No account exists until its address is confirmed. Every e-mailed link is single use and expires.

S.04

Secrets masked locally

Keys and tokens in the session are masked on your machine before anything is shared.

S.05

Sign out everywhere

See every browser, terminal and computer signed in, and end any of them, or all, in one click.

S.06

Leave whenever you like

Delete your account from your Account page. Your address and password are erased, not archived.

Read how Covo protects your data

What changed for us after the first week.

From our own sessions.

“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.”

Deniz, backend · Covo

“Our keys never left the laptop. That was the sentence that got security to say yes.”

Ulaş, founder · Covo

Free while we build it with you.

Every feature, for your whole team, while Covo is in beta. No card, no trial clock.

Public beta

Beta

For the whole team

For teams that want their agent sessions in one place.

$0USD / month
no card needed
Create your free account
  • Everything in Covo:
  • Unlimited shared sessions
  • Every supported coding agent 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

Questions, answered straight.

What Covo is, what leaves your machine and what the beta means.

What is Covo?

A shared workspace for an AI agent session. You keep running your coding 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, Codex and Cursor (watch, comment and approve tool calls through their hooks), 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 coding agent 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.

Read the docs

Make room for
your next big idea.

The beta is open. Every feature, free for your whole team.