Pairon · private beta
Claude Code team collaboration with Pairon
Work with Claude Code as a team in Pairon: connect a computer, share a conversation, assign participant roles, and review agent changes together.
By Pairon · Updated
Pairon gives teammates a shared conversation around Claude Code running on a connected computer. People can contribute instructions according to their role, follow the work, and review changes together. The Claude Code account and execution stay on the computer running that lane.
Set up a shared Claude Code workflow
The Pairon desktop app for Mac and Windows lists installed agents and can help install Claude Code from its publisher and guide you through sign-in. You approve the installation and use your own vendor account. Linux or a server uses the connection command shown in the Pairon browser app.
- Get beta access, sign in, and download Pairon for your computer.
- Approve the computer connection and allow the project folder.
- Set up Claude Code and sign in to its vendor account on that computer.
- Start a project conversation and select the lane with Claude Code.
- Invite a teammate as a Viewer, Collaborator or Admin for the access they need.
- Send a small instruction, contribute context, and review the completed change together.
Use the room to surface a missing constraint
The useful moment for collaboration is often before the agent edits. One teammate knows the failing behavior; another knows why the current implementation exists. Put both in the same conversation so the agent can account for that context.
Trace why an invited collaborator cannot open this project. Explain the failing authorization check before editing. Preserve workspace isolation and existing Viewer permissions. Another teammate will confirm the intended invite behavior. Make the smallest correction and report the relevant checks.
Illustrative instruction; adapt it to your project.
How this relates to Claude Code agent teams
Anthropic’s agent-teams feature coordinates multiple Claude Code instances, with separate contexts and communication between them. Pairon’s shared room addresses how human teammates participate around coding-agent work.
Decide which problem you need to solve: splitting a task among agents, bringing people into the working conversation, or both. Check Anthropic’s current documentation for its feature requirements and limits. Pairon does not claim to configure or manage Claude Code’s native agent-teams feature.
Understand whose account and permissions are used
An instruction sent to another person’s lane uses the agent account on that computer. Its owner consents to that use and can restrict who may send work there. Participant roles do not grant a new folder or higher computer permissions.
You can continue a Pairon conversation on a different connected computer or with Codex or OpenCode. That continuity uses the shared conversation and a brief; it does not mean every vendor receives an identical context window.
The published cost benchmark covers Codex only. Pairon has not published a measured Claude Code cost saving or a team productivity result.
Common questions
Does Pairon host Claude Code?
No. Claude Code runs on a computer your team connects, within the folders its owner allows. Pairon provides the shared conversation and coordination around that local agent.
Does each teammate need to share their login?
Pairon participants sign in to their own Pairon accounts. A lane uses the agent vendor account on its owner’s computer; sending work there requires that owner’s consent and permissions. Follow the vendor’s account and usage terms.
Sources and product details
Written by Pairon from the product behavior described below. Examples illustrate a workflow; they are not customer results.