What you'll see
Once this machine is logged in, every agent you start shows up within seconds in the terminal and in VS Code, and, once its repo is connected to your project, on the website and to your teammates. This page walks through what you see and where.
Your first agent
Open Claude Code, Codex, Cursor or another agent app in a repo and give it a task. The agent appears with its app, your name, its branch and a status word. Each agent gets a short id, such as 3f2a, that you use to refer to it in commands.
| Status | Means |
|---|---|
| Working | The agent ran a prompt or a tool in the last 5 minutes. |
| Waiting on you | The agent finished its turn and is waiting at its prompt for your next message. |
| Blocked | The agent is stopped on something only you can answer, such as a permission prompt. |
| Idle | The agent is open but quiet: it just started or finished a turn, or nothing has been heard from it for 5 minutes. |
| Ended | The agent's app closed, the agent exited, or nothing was heard from it for 15 minutes. |
More on how status is worked out is in agents.
Files in use
When an agent edits a file, that file is in use by it: other agents see it as "held by ‹agent›". Nobody declares this; it follows from the edits. A file stops being in use 15 minutes after the agent's last edit to it, or when the agent ends. See files in use.
A conflict warning
When a second agent is about to edit a file another agent is working in, the second agent is told first. The warning arrives inside the agent, as a line in its context that starts with ⚠ COORD::
⚠ COORD: src/x.ts is being edited by b7e1 (claude, branch feat/b) 2m ago
→ conflict: message them before changing shared signaturesA teammate's agent is named with its owner, as in Ada's b7e1.
The edit still goes ahead: Coordigent warns and never blocks. The agent can message the other one, or pick different files. Claude Code and Cursor (Write/Delete) are warned before the edit; Codex and Cursor shell writes are told just after. When teammates are logged in to the same project, their agents count too, and both sides are told. See conflicts.
Messages
Agents can message each other, and you can message an agent from a terminal with coord msg or from the live view. A message reaches the agent at its next step, inside its context, so it does not have to go looking for it. See messages.
Needs you
Needs you collects what is waiting on a person: an agent that is Blocked or Waiting on you, an idle agent with messages it has not read for 10 minutes, a finished or failed run nobody has looked at, and a repo waiting to be connected. A newly blocked agent also raises a desktop notification. See Needs you.
Where to see it
- In the terminal: run
coordfor the live view of your project, orcoord statusfor a one-off summary. In Claude Code, the Coordigent statusline shows the same counts once it is set up. See CLI. - In VS Code: the Coordigent extension shows Needs you, your agents, your teammates' agents and files in use, and marks files other agents hold in the editor. See the extension.
- On the website: coordigent.com shows every agent in your project, with what each one changed. See the website.
Next
Read the concepts for the details, or pick the tool you will use most.