Headless and CI

coord login normally opens your browser so you can approve the machine. A CI runner, a container or a remote box you reach over SSH has no browser, so it logs in with a CLI token instead. Everything else works the same.

#Get a CLI token

A CLI token is minted on the website by a signed-in person, and acts as that person in their project. Signed in, the button below mints a CLI token and shows the install command with it filled in. It is shown once.

# Set up Coordigent on this machine

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

Do these steps in order. Stop and tell me if any step fails.

1. Install the `coord` and `coord-mcp` binaries. Any directory will do:

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

   If `coord` is not found afterwards, start a new shell (the installer added
   it to the PATH) and try again.

2. Log this machine in:

       coord login

   It prints a code and opens my browser. Tell me to check that the code in
   the browser matches the one in the terminal and to click **Approve**. Wait
   for the command to finish; it finishes on its own once I approve.

   Never ask me for a token, never invent one, and never print, repeat or
   write to a file anything `coord login` saves. It is a credential.

3. Check the result:

       coord doctor

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

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

       coord connect

   That links the agent apps on this machine (Claude Code, Codex, Cursor and
   others) and registers the repo. Tell me which apps it linked.

5. Tell me to restart my coding agent.

   Coordigent is registered now, but an agent app reads its MCP configuration
   only at startup, so nothing appears until it restarts. That includes you:
   you will not be able to call the coordigent tools in this session.

The token is valid for 365 days by default. Each one is separate: minting another for a second machine does not affect the first. Coordigent stores only a hash of it, so a lost token cannot be shown again, only replaced with a new one.

#Install with the token

One command installs coord and coord-mcp, logs in, and runs coord connect:

Run it inside the repo, so coord connect also connects the repo to your project. Run anywhere else, it logs in and wires the agent apps on the machine, and you run coord connect in the repo afterwards. A runner has no one to answer the question Coordigent asks about a new repo, so connect it with coord connect.

The installer also reads the token from TOWER_TOKEN, which keeps it out of the command line and your CI logs. With the secret exposed as TOWER_TOKEN, the plain install does the same:

Other installer options, passed after sh -s --:

#Log in on a machine that already has coord

If coord is already installed, log in with the token directly:

Or log in and connect the repo in one step, inside the repo:

Both check the token with the server before saving it to ~/.tower/config.json, readable only by you. A token the server refuses stops with Login failed and saves nothing. Add --server <url> to either for a self-hosted server. coord login also starts the daemon in the background, without installing it as a service.

Without a token and without a terminal, coord connect does not try the browser. It stops and tells you to use coord login at a terminal, or coord connect --token.

#Environment variables

A CI machine can skip ~/.tower/config.json and take its login from the environment:

When TOWER_TOKEN and TOWER_SERVER_URL are both set, coord and coord-mcp use them and ignore any saved login. When only one is set, it overrides that one field of the saved login. coord-mcp also accepts COORDIGENT_TOKEN and COORDIGENT_SERVER_URL, which win over the TOWER_* names; To take its login from the environment, coord reads only TOWER_TOKEN and TOWER_SERVER_URL, so set those.

#No questions asked

With no terminal, coord connect asks nothing and picks safe defaults:

• Repo files. It writes none, unless you add --repo-files. Then it writes Claude Code's files, and those of any client the repo already uses, such as a repo with a .cursor/ directory. Name others with --clients, for example coord connect --repo-files --clients codex.
• The background daemon. It does not install the daemon as a login service. The agents' hooks start the daemon when they need it, so nothing else is required on a short-lived runner. --daemon-service installs the service anyway, and --no-daemon-service records that you do not want it and removes one already installed.

#Without an account

Coordigent also runs with no login at all. Agents on the same machine still see each other, the files each one holds, and their messages, and nothing leaves the machine. coord doctor reports this as Mode: local. Log in when agents on other machines need to see this one.

#Next

• Runs covers starting headless agents that Coordigent supervises.
• CLI reference lists every coord command and flag.
• Install Coordigent covers the normal install on a laptop.