Install Coordigent

One command installs Coordigent on a machine. Run it once per machine, in any directory.

#What it installs

The installer downloads two programs and puts them in ~/.tower/bin:

• coord, the command line tool. You use it to log in and watch your agents. Your agent apps also run it through hooks to report what they do.
• coord-mcp, the MCP server your agent apps start. It gives each agent the coordigent.* tools: see who else is working, check files, send messages.

Each download is checked against the checksum the server publishes before it is made executable. A download that does not match is deleted and the installer stops. If the server publishes no checksum, the installer says so and installs unverified.

The installer adds a PATH line to existing zsh, bash and sh startup files. On a fresh machine, it also creates the current shell's startup file: .zshrc for zsh (under ZDOTDIR when set), .bashrc and .profile for bash, or .profile for sh. Existing bash login profiles are updated too. New shells find coord through this line:

It adds the line once and never rewrites it. Open a new terminal, or run ~/.tower/bin/coord directly, if coord is not found right after installing. If the install directory is already on PATH, it leaves startup files alone. If a startup file cannot be created or updated, it warns and finishes installing; use the printed executable path and add the PATH line yourself. --no-path-update skips startup-file changes entirely.

On a machine that has never logged in, the installer also writes ~/.tower/config.json with the server it came from and no token, so coord login and coord update use that server. If the file already exists it is left alone; when it names a different server, the installer says which one this coord uses and how to switch (coord login --server <url>).

Nothing else on your machine changes until you run coord login. If this machine is already logged in, the installer runs coord connect for you at the end. That wires your agent apps again with the new binaries and, if you ran it inside a repo, connects that repo too.

#Options

Pass options after sh -s --. --bin-dir <dir> installs somewhere other than ~/.tower/bin, and --no-path-update leaves your shell files alone.

#Supported platforms

The installer needs curl or wget, and sha256sum or shasum to check the download.

#Why ~/.tower

Coordigent keeps everything it knows about this machine in ~/.tower: your login, the background daemon's files, the record of local agents, and the binaries. The directory has an older name than the product. It kept that name so that every existing install keeps working. Set TOWER_DIR to move it.

#Keep it current

coord update downloads the current coord and coord-mcp, checks them, swaps them in place and restarts the background daemon. It needs no login.

coord update --check only tells you whether an update is available.

#Check the install

coord doctor checks each agent app on this machine, whether you are logged in, and whether the daemon is running. Most failing lines name the command that fixes them.

#Remove it

coord uninstall removes Coordigent from this machine: the daemon, its hooks and MCP entries in your agent apps, the rules it wrote, and ~/.tower. Add --dry-run to see the plan first, or --keep-data to keep everything in ~/.tower except the binaries. Anything you edited by hand is kept and named.

To stop Coordigent in one repo only, or to take a repo out of your project, see Connect a repo.

#Next

Log in to connect this machine to your project. Setting up a machine with no browser, such as a CI runner? See headless and CI.