Agents

An agent is one running coding-tool process: one Claude Code window, one Cursor agent, one Codex or Kiro run. Coordigent records each agent on your machine and, when you are logged in, shows it to everyone in your project.

#What Coordigent knows about an agent

• The client it runs in (claude, codex, cursor, kiro).
• The person who started it and the machine it runs on.
• Its repo, branch and worktree.
• The files it has edited, and the files it holds right now (Files in use).
• Its status.

Each agent is shown with a short id: the first characters of its full id, at least four (for example 3f2a), and more when another agent in the project starts the same way. Codex agents usually get six or eight. Commands that take an agent, such as coord sessions stop and coord msg, accept any start of its id that is four characters or longer and matches only one agent.

#Status

Every surface uses the same five words.

Waiting on you and Blocked do not turn into Idle with time. They change only when the agent does something new, its process exits, or it is silent for 15 minutes. Both put the agent on the Needs you list.

Which states a client can report depends on its hooks. Claude Code reports all five. Codex and Kiro cannot report Blocked, and they have no waiting notification, so they count as Waiting on you once a finished turn has been quiet for 60 seconds.

When you message from a terminal or the live view, Coordigent lists you as a session too. It always reads Idle, never counts as working, and End idle agents leaves it alone.

#Where agents show up

• CLI. coord opens the live view, whose AGENTS pane lists your project's agents. Press L for this machine's agents. coord sessions (alias coord ps) prints every agent on this machine; coord status prints the project's agents once.
• Your agent. The coordigent.status and coordigent.session.list tools return the same list. The status block marks the caller's own row (you), and coordigent.session.list sets you: true on it.
• VS Code. The Coordigent views list agents grouped by repo, with status, branch and edited files.
• Website. Your project's pages show every agent live, with a record of each one.

#How an agent starts and ends

An agent appears on its own when you start a coding tool in any repo on a machine you ran coord login on; there is nothing to register by hand. Your teammates see it once the repo is connected to your project. It ends when the tool exits. If the process dies without saying so, for example when you close the terminal, Coordigent notices the process is gone and ends the agent.

You can also end or stop one yourself:

The person who started an agent, and the project's owner and admins, can also end it from the website.

#Next

• Files in use
• Needs you
• CLI reference