Install
Dashboard

Log in

coord login signs this machine in to your Coordigent project. You approve it in your browser: there is no token to copy or paste. Run it once per machine.

coord login

What happens

  1. coord login asks coordigent.com for a one-time code and prints it in your terminal.
  2. It opens your browser at https://coordigent.com/device?code=….
  3. If you are not signed in on the website, sign in first. You come back to the same page.
  4. The page asks you to approve this machine. It shows the machine's name, its operating system, the coord version, the code, and the project the machine will join.
  5. Check that the code on the page matches the one in your terminal, then click Approve.
  6. The terminal sees the approval within a couple of seconds and saves the login.
  7. It wires this machine: the coordigent MCP server in each agent app installed here, and Coordigent's hooks at user level, so agents in every repo can coordinate. See Connect a repo.

The terminal shows something like this while it waits:

COORD · login · coordigent.com ──────────────────────────────────────────────── ✦ Your code WXYZ-2345 Opened https://coordigent.com/device?code=WXYZ-2345 Check the code matches, then approve this machine. → Waiting for approval… (Ctrl-C to cancel)

And once you approve:

● Logged in as Ada Lovelace · Ada's project Next coord connect run it inside your repo, then open Claude Code, Codex or Cursor there coord live view of your project

If this machine has repos connected already, login names them instead (Already connected on this machine: web, api. Open an agent in one.) and offers coord connect for any other repo. The browser's "Return to your terminal" card says the same.

Then come the lines for the agent apps it wired, as in Connect a repo.

The machine joins the project you are looking at on the website when you approve. If you belong to several projects, switch to the right one first.

If the browser does not open

Over SSH, or on Linux without a display, coord login cannot open a browser. It prints the address instead: open it on any machine where you can sign in, check the code, and approve.

The code is good for 10 minutes. If it expires, or someone clicks Deny, coord login stops and says so. Run it again for a new code.

Where the login is kept

The login is saved in ~/.tower/config.json, readable only by you. A token in it is what "logged in" means to every coord command and to your agent apps; before you log in, the file may hold only the server the installer came from. Without a login, Coordigent still works on this machine alone, with no account.

Each approved machine gets its own login, named after the machine, so logging in on a second machine does not sign out the first.

Signing in on the website

On coordigent.com you sign in with GitHub, Google, or a link sent to your email. The first time you sign in without an invite, Coordigent creates a new, empty project for you. To join someone else's project, use their invite link instead: see Invite teammates.

Machines with no browser

CI runners and servers where nobody can approve in a browser log in with a token instead. See headless and CI.

Next

Restart your agent app and start working. Connect a repo explains how a repo joins your project.