AgentMash for Coordinating AI Coding Agents

What does AgentMash do, in plain English?

AgentMash gives a development team a shared view of its AI coding agents. If one person uses Claude Code and another uses Codex or Cursor on the same repository, it helps each agent understand what the others are changing.

Think of it as a coordination desk for an existing coding workflow. Your agents still do the coding under your own accounts. AgentMash adds activity reports, file ownership claims and contextual warnings so the team can discuss overlapping work earlier.

Coordinate edits before they turn into merge work

An agent can learn that a teammate recently changed the same file, which branch contains the work and what task prompted it. Planned path claims help divide a larger task before both sides start editing. If work still overlaps, reconciliation tells a person to examine both changes before integration.

The ordinary advisory is guidance rather than an exclusive file lock. Review and tests remain part of accepting a change. Symbol-based checks concentrate on JavaScript and TypeScript exports; Python, Go and Rust rely on path matching. For parallel sessions under your own identity, consult AGENTMASH_WARN_SELF=1: your other sessions are excluded by default, and adapter limitations apply.

The service is in beta. If the coordination server cannot answer, hooks let work continue, so an unavailable warning must not be treated as proof that no one else is editing.

Connect a repository and verify the first session

Use a repository you are authorized to connect and an existing coding-agent account.

1. Someone with GitHub push access connects the repository through the official web installer.
2. With Node.js 18.12 or later installed, each developer runs npx agentmash login and completes GitHub sign-in.
3. Run npx agentmash status inside the repository to check the account and connection.
4. Approve the required hooks or MCP connection and restart the agent. Codex also requires approval through /hooks.
5. Start a small task and confirm its activity appears in the room before relying on collaboration warnings.

The lobby still needs the hooks for edit reporting. User-level login does not commit setup files to the repository; npx agentmash logout removes those connections. Follow the agent-specific setup instructions for differences.

Use a shared agent workspace and specialist crew

The macOS and Windows lobby brings sessions and team presence together; Linux users can connect through the CLI. A request to a teammate’s agent needs that teammate’s approval and runs on their machine and account, with their tool approvals.

The optional crew provides 22 specialist Claude Code agents for planning, implementation, testing, review and other jobs. Adding a crew writes files into the repository so teammates can share the configuration. Developers can also use the documented API and MCP tools to query activity, check intended edits or report events. Adapter behaviour differs: Cline receives advice after an edit, while Continue and Zed use MCP queries.

Know what the room receives

Local source code does not mean no data is shared. The room normally receives paths, branches, change counts, touched names and the first 500 characters of a prompt. AGENTMASH_HINTS=0 withholds ordinary prompt hints, subject to shared-session exceptions.

Enabling diffs or sharing a live session changes what leaves the machine; AGENTMASH_DIFFS=0 vetoes sending your diffs. Teammate request text and reply summaries are stored server-side without end-to-end encryption. Read the data-sharing explanation before using a confidential project.

Free limits and the real cost of a team

Checked on November 3, 2026: Free allows two developers, one private repository, unlimited public repositories and agents, and seven days of history. Team lists USD 20 per developer per month billed monthly, or USD 16 per month billed annually at USD 192 per year, with applicable tax added.

Team can retain up to 90 days, but an administrator must raise the room’s default seven-day setting. Model subscriptions are separate. Self-hosting is offered under Enterprise agreements. Check the current plans and billing conditions for the final cost.

Questions developers ask

Does the free plan include the coding models?

No. AgentMash coordinates agents you bring; their subscriptions and model usage follow their own pricing.

Will AgentMash automatically prevent or merge conflicts?

No. Default warnings and reconciliation expose overlap. They do not guarantee conflict-free work or automatically merge both changes.

Does my source code leave my machine?

Not by default as full source files, but metadata and prompt excerpts are shared. Optional diffs and live sharing have different data boundaries.

Official setup and developer resources

• Documentation: setup, supported adapters and limitations
• Public API: room checks and custom integrations
• Crew: specialist roles and team configuration