Set up / one machine

Install Coordigent.

Three steps. Keep the editor you already use.

  1. Get your command

    One line per machine, with your token already in it. Nothing to copy out of a settings page.

    Your install command
    you@laptop: ~ — zsh

    # Install Coordigent. Connect your coding clients.

    Sign in to get your command, with your token already filled in.

    Get started
    Or have an agent set it up for you

    # Paste into Claude Code, Codex or Cursor. It asks you for the install command when it gets there, so your token stays out of the transcript.

    Set up Coordigent on this machine for me.

Coordigent coordinates several AI coding agents working on one repo: it shares
which files each session is holding, warns when two sessions reach for the same
file, and lets sessions message each other.

Please do this, and stop and tell me if any step fails.

1. Ask me for my install command, and wait for it.

   I get it from https://coordigent.com/install after signing in. It is a
   one-line "curl ... | sh" with a personal token in it.

   Do not guess it, do not invent a token, and do not write it into a file or
   repeat it back to me — it is a credential, and this conversation is kept.

2. Run the command I give you, in a shell. Any directory will do.

   It installs "coord" and "coord-mcp", signs this machine in, and registers
   Coordigent with every agent app it finds here.

   If "coord" is not found afterwards, it is on the PATH the installer just
   added — start a new shell and try again.

3. From the root of the repo I am working in, run:

     coord init

   That sets the repo up: MCP config, rules and hooks for the clients on this
   machine, and it registers the repo.

4. Check the result:

     coord doctor

   It prints a pass or a fail for each client, and the fix for anything that
   failed. Tell me what it said, and carry out any fix it names.

5. Tell me to restart my coding client.

   Coordigent is registered now, but a client only reads its MCP configuration
   at startup, so nothing will appear until it is restarted. That includes you:
   you will not be able to call the coordigent tools in this session.
    Your personal token is included after sign-in. No manual setup.

    Run it once per machine, then pick your client below. Setup guide →

  2. Run it

    It installs coord and coord-mcp into ~/.tower/bin, signs this machine in as you, and registers Coordigent with every supported client it finds — Claude Code, Cursor, Codex, VS Code, Kiro, Windsurf and Perplexity. If it cannot support your machine it says so rather than half-installing.

    Then coord init in each repo you want on the desk.

    ~/.tower is the state directory, named before the product was. It is left as it is because renaming it would break every existing install.

  3. Check it took

    A healthy setup reports PASS for Config, Server and User MCP, and names the clients Coordigent registered.

    Verify the install
    coord doctor

    Then start a session in your editor and open your team — it appears there within seconds.

    Update later
    coord update

Set up one client

Step 2 registers every client it finds. This is what it wrote, per client — and the line to run for the ones you install by name.

Claude Code / what you get

Bring your tools.

  • A coordigent entry in ~/.claude.json, alongside any MCP servers you already had.
  • Hooks that tell your session when a teammate is on the same file.
  • A statusline showing live sessions, and the coordigent.* tools in every session.
Connect Claude Code
coord connect
In each repo
coord init

Already installed? Re-run it to reconnect. It registers every client it finds. Get your install command →