Coordinate coding agents across a team

How a team running Claude Code, Codex and Cursor on one repo sees every teammate's agents, avoids editing the same files and lets agents message each other.

Short answer

Short answer: When several people each run coding agents on the same repo, put everyone in one Coordigent project. Every teammate's agents then appear live in the terminal, VS Code, the website and Slack; an agent about to edit a file a teammate's agent holds is warned and told whose agent it is; and agents and people can message any agent in the project. Each person keeps their own tools: Claude Code, Codex, Cursor, Kiro or Windsurf.

Most parallel-agent tools stop at one machine. The conflicts that hurt most are between two people who each assumed their agent had the area to itself.

1. Each person installs and logs in

curl -fsSL https://coordigent.com/install | sh

The installer signs you in, links the agent apps on the machine and connects the repo to your project. See Log in.

2. Invite the team

Click Invite in your project on the website and send teammates the link or the eight-character code; they sign in and join the same project. See Invite teammates.

a link or an eight-character code

3. What everyone gets

  • One picture of the work. Every agent in the project, whose it is, its branch, its status (Working, Waiting on you, Blocked, Idle, Ended) and the files it holds. See Agents.
  • Warnings across machines. The server compares teammates' agents' edits, so a conflict between your agent and a teammate's reaches both agents. See Conflicts.
  • Code owners hear about it. When someone's agent edits files CODEOWNERS gives to you, your live agents are told. Advisory only; nothing is blocked.
  • Agents that talk. An agent can message a teammate's agent, you can message any agent from the terminal, VS Code, the website or a Slack thread, and coord takeover picks up a teammate's agent's work with its context. See Messages and Handoffs.
  • Slack. A channel that mirrors agents, conflicts and messages, with replies going back to the agents. See Slack.

What Coordigent records

File paths, prompts sent to the agent (up to 100 KB), the commands it runs (not their output) and size-capped diffs. Full transcripts never leave the machine. See Security.

transcripts never leave the machine