For engineering teams using Claude Code
Run Claude Code as a team.
PairWave is a shared browser workspace for Claude Code. Sessions run on your own machines through the Relay desktop app. Your team watches them live, approves tool calls, reviews Claude's edits line by line and steers from any browser.
$15 per seat per month. 7-day trial, no card.
Plan: sign with the new key, accept either key when verifying, and retire the old one after the longest socket lifetime. Starting with the loader.
- Read src/lib/keys/loader.ts
- Edit src/lib/keys/loader.ts +12 −3
- Edit src/lib/keys/verify.ts +8 −2
alice (team only, Claude doesn't see this) @andy@acme.devI'll review once it pushes.
The session view: live transcript, a pending approval, the queue and the controls under the composer.
How it works
- 1
Pair a machine
Install the Relay desktop app where you code and approve its short code at /pair. It dials out to the hub, with no SSH or inbound ports, and keeps itself up to date.
- 2
Start Claude Code from the browser
Pick a folder on any paired machine and spawn a session. It streams onto your dashboard while it runs.
- 3
Bring the team in
Share a session by email: can view, can comment, can prompt or can approve. Everyone sees the same transcript in real time.
Collaboration
One live session, with the whole team on it.
Claude's remote control gives one person one session. PairWave puts a running session in front of everyone who should see it, and gives each of them a specific job.
| Role | Can |
|---|---|
| Can view | Watches the live transcript |
| Can comment | Comments on Claude's changes, can't prompt |
| Can prompt | Sends and queues prompts |
| Can approve | Allows or denies tool calls and plans |
Approvals in the browser
Gated tool calls arrive with the exact command. An approver clicks Allow and Claude Code carries on, on the operator's machine.
Plan approval
When Claude finishes a plan in plan mode, you get a plan card with the same choices Claude Code offers in the terminal.
Team-only chat and @mentions
Talk next to the transcript without Claude reading along. Mentions only notify people who can already see the session.
Review requests and handoff
Ask for a review or hand the session to someone who can drive it. Open requests land under Needs you on their dashboard.
Parallel runs
Hand one task to five agents. Keep the best result.
Start a task on 2 to 5 Claude Code sessions at once. Each runs in its own git worktree so they can't overwrite each other, with its own model and thinking level. Start from a GitHub, Linear or Jira issue if you like.
- Thinking
- High
- Worktree
- run-412-a
- Changes
- 7 edits
- Thinking
- Medium
- Worktree
- run-412-b
- Changes
- 11 edits
- Thinking
- Max
- Worktree
- run-412-c
- Changes
- 4 edits
Clear this interval on shutdown or the test runner hangs.
Review
Review Claude's edits while it's still working.
The Changes tab turns every edit Claude makes into a diff. Comment on the lines that need work, and someone who can prompt sends the batch back to Claude as one prompt. When it looks right, Commit, Push and Open PR are one click each.
- Checkpoints. Snapshot the working tree to a hidden git ref without touching your branch, index or stash.
- PR and CI panel. Link the PR, watch its checks and send failures to Claude with the Actions log attached.
- Screenshot notes. Draw numbered boxes on a pasted screenshot and send it with matching notes.
Diffs come from Claude's own edits, not a full git diff. Git actions still go through Claude Code's permission prompts.
Controls and automation
The desktop app's controls, plus the work that runs without you.
Under the composer
- Permission mode
- Ask before edits, accept edits, plan mode or auto.
- Model and thinking
- Switch model and thinking level mid-session.
- Slash commands
- Type /compact or any other command from the composer.
- Stop
- Interrupt Claude mid-step, like pressing Esc.
- Working indicator
- Shows the step in flight, like Running pnpm test, and time elapsed.
- Queue
- Line up prompts while Claude is busy. Each goes out as the person who wrote it.
While nobody is watching
- CI auto-fix
- Failing checks on the linked PR go to Claude on their own. Once per commit, at most three attempts, off when the PR closes.
- Scheduled prompts
- Send a prompt once, hourly or daily. Missed repeats are skipped, not piled up.
- Always-allow rules
- Let a tool through for the rest of a session. Shell rules match a command prefix and never match chained commands.
- Idle compaction
- Quiet sessions are compacted so the next prompt starts from a smaller, cheaper context.
Each automation acts as the named person who turned it on, and stops if they lose access.
Plan limits
See your real Claude limits before you hit them.
With Relay installed, each session reports your actual 5-hour and weekly plan usage, with reset times, and how full the context window is. Team admins see every member's usage, so work can move to whoever has room.
Every session also shows token use by model and estimated cost, and you can opt in to a private weekly report by email.
Also in the box
- Command palette
- ⌘K to jump to sessions, run actions and search transcripts.
- Full-text search
- Every transcript you can see, straight to the exact turn.
- Installable app
- Add PairWave to your dock or home screen as a web app.
- Browser notifications
- Opt in to hear about approvals, plans and replies.
- Writeups and lessons
- Turn a good session into a lesson with an owner and a review date.
- Machine controls
- Restart, switch mode, peek at the terminal or kill from the Machines page.
Trust
Shared control, with a record of who did what.
Every prompt, approval, scheduled send and automatic fix is recorded against the person it acts for. There is no shared bot account.
Owners can open any team session for governance, and every owner view is logged in the session's audit trail with a reason.
Relay gets its own per-machine token. PairWave never sees your Anthropic API key, and unpairing a machine revokes its token.
- 14:22andy (owner) viewed the sessionReason: investigating high spend last week
- 14:22system recorded the owner view in the audit trail
- 14:31ren allowed Bash: git push origin vault-key-rotation
- 14:40alice sent 2 review comments to Claude
Questions
What is PairWave?
PairWave is a shared browser workspace for Claude Code. Your Claude Code sessions run on your own machines; PairWave lets your team watch them live, send and queue prompts, approve tool calls, review Claude's edits and run the same task on several agents at once.
Does PairWave run Claude Code in the cloud?
No. Sessions run on your own machine through the Relay desktop app, which you pair with PairWave once using a short code. The machine dials out to the hub, so you don't open any inbound ports, and PairWave never holds your Anthropic API key.
Can I bring in a Claude Code session I started in the terminal?
Yes. Relay lists the Claude Code conversations on each paired machine from the last 30 days, including ones started in a terminal or the Claude desktop app. Pick one, file it under a project, and it continues in PairWave with its earlier history.
Can teammates take over my session?
Only with the role you give them. “Can view” watches, “Can comment” comments on changes, “Can prompt” sends prompts and “Can approve” allows or denies tool calls and plans. Mentions, review requests and handoffs never grant access on their own.
How do parallel runs work?
You start one task on 2 to 5 Claude Code sessions. Each runs in its own git worktree with its own model and thinking level, gets the kickoff prompt as soon as it connects, and you compare the results side by side.
How do I keep Relay up to date?
Relay checks for new versions itself. When one is out, its menu offers to update, and the update installs and restarts Relay without pairing the machine again. On Linux, run relay update.
Where do the diffs in the Changes tab come from?
From Claude's own file edits in the session. They show what Claude changed, not edits made outside the session. Commit, Push and Open PR ask Claude to run the git commands, which still go through Claude Code's permission prompts.
How does PairWave know my Claude plan limits?
The Relay app reads Claude Code's status line and reports your real 5-hour and weekly plan usage, with reset times, plus context-window use. Without Relay, PairWave shows estimated spend from token counts instead.
How much does PairWave cost?
$15 per seat per month, billed per team. Every new team gets a 7-day trial with no card required. Claude usage itself stays on your own Claude plan.
How do I sign in?
With GitHub, Google or an email magic link. Each one verifies your email, and the same email always lands on the same account.
Pricing
One plan for the whole team.
$15per seat per month
Billed per team. Start with a 7-day trial, no card needed. Claude usage stays on your own Claude plan; PairWave doesn't resell it.
Included
- Shared live sessions with view, comment, prompt and approve access levels
- Parallel runs on 2 to 5 agents in separate worktrees
- Resume Claude Code conversations started outside PairWave
- Changes review, checkpoints, and the PR and CI panel
- CI auto-fix, scheduled prompts and always-allow rules
- Relay plan limits, team usage view, cost tracking and weekly reports
- Writeups, lessons and logged owner access
- Light and dark themes, an installable app and push notifications