Connect a repo

After coord login, agents in every repo on this machine can see and message each other here. But each repo has to be connected once before Coordigent records what happens in it and your teammates' agents see yours: say yes to the one question its first agent raises, or run coord connect in it. Until then the server keeps nothing from that repo.

#What coord login already did

coord login wires the whole machine, once:

• It finds the agent apps installed here — Claude Code, Codex, Cursor, Kiro and, on macOS, Claude Desktop — and adds the coordigent MCP server to each one's own settings, so the Coordigent tools appear in every repo you open with it.
• It adds Coordigent's hooks to the user-level hook files of Claude Code (~/.claude/settings.json), Cursor (~/.cursor/hooks.json) and Codex (~/.codex/hooks.json), so agents in every repo report their edits and status. Your own hooks in those files are kept. Kiro and Claude Desktop have no user-level hook file and get the MCP server only. Windsurf and VS Code (Copilot) are not wired by coord login; their pages say how to add them.

Nothing is written into your repos.

#The question

The first time an agent works in a repo this machine has not connected, Coordigent asks once, as a Needs you item, whether to connect the repo to your project. It does not ask about a repo a teammate has already connected: that repo is in the project already.

In VS Code it arrives as a notification with three answers:

The Needs you row's menu also has Don't connect this repo, which stops the question for that repo for good. In the terminal the same item shows in coord status and coord sessions; answer it by running coord connect in the repo.

Connecting registers the repo with the project you are looking at on the website and writes no files. Until a repo is connected, its agents coordinate on this machine only and nothing they do is recorded.

#Connect a repo now

To connect a repo without waiting for the question, run this inside it:

It does what coord login did for the machine, then connects the repo:

✓ means linked, – means the app is not installed here and was skipped, and ⚠ means the app's settings file could not be updated; the line says why. ChatGPT is not linked: it accepts only remote MCP servers, and coord-mcp runs on your machine.

If this machine is not logged in yet and you are at a terminal, coord connect runs coord login first (Log in), then carries on. Run outside a git repo with an origin remote, it wires the machine but connects no repo, and says so.

A project can hold several repos: connecting another one adds it to the project you are looking at, next to the ones already there.

#Files to commit, if your team wants them

coord connect --repo-files also writes Coordigent's files into the repo, for teams that commit them so every clone has them:

• hooks in .claude/settings.json, and the Claude Code statusline;
• the coordigent entry in .mcp.json;
• a marked Coordigent block in CLAUDE.md telling agents how to coordinate, and a few slash commands and a skill under .claude/;
• the same hooks and rules for Cursor and Codex when the repo already uses them (.cursor/, .codex/). Add others with --clients, for example coord connect --repo-files --clients cursor,codex.

Running it again updates the files in place. A block you edited by hand is left alone, and the command tells you so; --force replaces it. What each app gets is on its own page: Claude Code, Codex, Cursor, Kiro and others.

#Keeps Coordigent running

The first time, coord connect asks whether to keep Coordigent running in the background. Yes installs the daemon as a login service, so it is always on. See this machine.

#Restart your agent app

Agent apps read their MCP settings when they start. Quit and reopen Claude Code, Cursor, Codex or whichever app you use, then open it in the repo.

#Check it worked

coord doctor checks every agent app this repo uses, your login and the daemon. Most failing lines name the command that fixes them.

#Stop Coordigent in a repo

coord unenroll, run inside a repo, turns Coordigent off for you in that repo, on this machine only:

From then on your agents there are no longer recorded or warned, the files they held are released, and teammates no longer see their edits. Every worktree of the repo is covered, and Coordigent never asks to connect it again. Your teammates, the project and any files committed to the repo are untouched. In VS Code, the same is Coordigent: Unenroll this folder.

To turn it back on, run coord connect in the repo, or use Connect this repo in VS Code.

#Remove a repo from the project

coord repo remove takes the repo you are in out of the project for everyone. Only the project's owner can; anyone else is told who to ask.

It asks first. Live agents in the repo are ended and the repo leaves the project, but its history is kept: the owner running coord connect in it brings everything back. It also stops Coordigent for you in the repo on this machine, as coord unenroll does.

coord repo remove --delete-history deletes the repo and all of its history for good. It asks you to type the repo's owner/name first; from a script, pass it as --confirm <owner/name>. In VS Code, Coordigent: Remove repo from project… offers both.

To take Coordigent off this machine altogether, see Install.

#Next

Invite teammates to your project, or start an agent and see what you'll see.