# Coordigent: product reference > Coordigent provides coordination infrastructure for AI coding agents working in parallel on a shared GitHub repo. The product is Coordigent. It installs two binaries: `coord`, the command-line tool, and `coord-mcp`, the MCP server a coding client talks to. There is no binary named "Tower"; the name survives only in the `~/.tower/` state directory those binaries install into. Website: https://coordigent.com/ Public setup guide: https://coordigent.com/install Last updated: 2026-09-17 ## What Coordigent does Coordigent is an MCP server that makes coding agents aware of each other's work. It sits on top of the tools and GitHub repos a team already uses. A team can use different coding clients while coordinating contributions to one repo. Capabilities include: - Agent-to-agent messaging: agents exchange context and coordinate who handles which work. - File overlap warnings: an agent can learn that another active agent is editing a file before making a competing change. - Shared file state: agents and teammates can see which sessions are working on which files across the team. - Shared-repo coordination: multiple agents can contribute commits to one existing repository rather than requiring a separate repository per agent. - Tool discovery: a team-curated catalog where agents find tools and capabilities. It is a searchable directory; it performs no install and takes no payment. An overlap warning provides context for coordination. It does not guarantee conflict-free changes or replace Git review, tests, or human decisions. Coordigent observes; it does not act on a team's repositories. It never writes to git, opens pull requests, or changes branches. ## Supported platforms Coordigent is model-agnostic and works with Cursor, Codex, Claude Code, VS Code, Kiro, Windsurf, and Perplexity through MCP and client integrations. Operating systems: macOS on Apple Silicon (`darwin-arm64`) and Linux x86_64. Windows and Intel Macs are not supported yet. The installer refuses a machine it cannot support and says so, rather than half-installing; the source can be built directly with `bun run build:cli`. `coord-mcp` is what connects a coding client to Coordigent, and `coord` is what installs and inspects it. The public setup guide describes the client-specific steps. Slack is available, and a customer registers nothing: the Slack app belongs to Coordigent. A team signs in, opens team settings, chooses Connect Slack, approves the app in their Slack workspace, and selects a channel; verbosity and quiet hours are set on the same card. The channel then receives one dispatch sheet per team per day, edited in place, with each conflict as its own thread — a reply in that thread reaches the agents involved. The slash commands are `/coordigent status`, `/coordigent claim [id]` and `/coordigent msg `. Coordigent must be invited to a private channel before it can be selected, and Slack Connect (externally shared) channels are not supported. Microsoft Teams requires an app registered against the customer's own Microsoft 365 tenant by an administrator, so it should not be described as universally available in the way Slack is. ## Intended users The primary audience is engineering teams of 2–50 engineers where several people run AI coding agents on the same codebase. Coordigent helps teammates understand agent activity and coordinate overlapping work across clients. ## Example workflow A teammate runs Claude Code while another runs Cursor against the same GitHub repo. Each session connects to Coordigent. Agents can check shared file state and communicate about their work. If both approach the same file, overlap information helps them agree on ownership or sequencing before continuing. The team keeps its existing repo and coding clients. ## Installation and documentation 1. Open https://coordigent.com/install#get-command and sign in. 2. Copy the personal install command provided by the site, with the token already filled in. 3. Run the command on the machine where the coding clients run. It installs `coord` and `coord-mcp` into `~/.tower/bin` and registers Coordigent with every supported client it finds. 4. Run `coord init` in each repo you want on the desk. It writes MCP config, rules and hooks for every detected client. 5. Run `coord doctor` to check the installation, then start a session in the editor. To update to the latest binaries later, run `coord update`. The current public documentation is the installation guide. Product capabilities, pricing, and common questions are on https://coordigent.com/. No separate public API documentation URL is asserted here. ## Joining an existing team A member of a team creates an invite, which is an eight-character code such as `W8EM-CP55`. It is entered at https://coordigent.com/join, or followed directly as https://coordigent.com/join/W8EM-CP55. A code works once and lasts seven days. Signing in without a code creates a new team of one. ## Privacy Session transcripts stay on the machine that produced them. The server stores a structured record of what changed — sessions, files touched, overlaps, messages — not the conversation itself. ## Pricing - Solo: free tier. - Teams: $5 USD per seat per month. ## Founders Coordigent was founded by Ali Hussain (CEO) and Krish Dhanuka. Both are ex-Amazon and affiliated with UT Austin. ## Product boundaries Coordigent coordinates agents inside existing tools and repos. It does not require migrating to a new chat application or Git host. `coord` and `coord-mcp` are plumbing, not a coding model. MCP client support does not imply endorsement or a partnership with the client vendor. ## Reference links - [Product overview and common questions](https://coordigent.com/) - [Installation and client setup](https://coordigent.com/install) - [Personal install command](https://coordigent.com/install#get-command) - [Join a team with an invite code](https://coordigent.com/join) - [Short product reference](https://coordigent.com/llms.txt)