Install
Dashboard

Runs

A run is an agent that Coordigent starts and supervises on your command, in a new git worktree on a new branch. It is headless by default and comes back with a result, or it opens in its own terminal window for you to watch.

Two kinds of run

  • Headless. Coordigent starts Claude Code (claude -p) or Codex (codex exec) with no terminal, watches it to the end, and collects a result: a summary, the branch, the files and the diff.
  • Interactive (--interactive). The same new worktree and branch, but a normal agent opened in a terminal window that you watch and type into.

A run starts only when you ask. Nothing starts, restarts or resumes one on its own, because it spends your model credits. A run writes only a new local branch and never pushes.

Starting a run

Start a headless run from this checkout; returns at once

coord sessions start "add a test for parseConfig"

Continue another agent's work and follow progress

coord sessions start --from a3f2 --wait "finish the TODOs"

Open the run in a new terminal window instead

coord sessions start --interactive "add a test for parseConfig"

The run branches from your checkout's current commit, so it does not see uncommitted changes; Coordigent warns you when there are some. With --from, it branches from that agent's branch and its prompt carries that agent's handoff. --client codex runs Codex instead of Claude Code.

One headless run goes at a time. A headless run is stopped after 30 minutes.

While it runs

A run is an agent like any other. It holds the files it edits, warns and is warned about files in use, and can be in a conflict with your own agents. You can message it with coord sessions message. coord sessions marks it run <id>.

A headless run cannot ask you anything, so its permissions are fixed up front: it may edit files in its worktree and use an allowed list of tools. A tool call outside that list is denied and the run carries on; the denials are listed in its result. Add tools for one run with --allow-tool <pattern>. If the run is stuck on a decision, it stops and lists Questions for you: in its summary.

When it ends

A headless run ends done, failed, stopped or timed_out. Anything left uncommitted is committed on the run branch, the worktree is removed, and the branch stays. Unless you stopped it yourself, you get one desktop notification, and the run sits on your Needs you list until you open it.

What is going and what finished

coord runs

The result, with the diff

coord runs show <id> --diff

Stop a run that is going

coord runs stop <id>

Delete a finished run's branch, worktree and record

coord runs discard <id>

Clear finished runs older than 14 days

coord runs prune

An interactive run has no supervisor, timeout or automatic commit. It ends when you close its agent; its worktree and branch are always kept. Stop it by closing its window, or with coord sessions stop <agent>.

A run branch you have changed by hand, checked out elsewhere or pushed counts as yours, and Coordigent never deletes it unless you force it with --force.

Where you see runs

  • CLI. coord runs, and run <id> markers in coord sessions.
  • VS Code. The Runs view lists runs going and finished, with Start headless agent…, Show run result…, Stop run… and Discard run….

Next