CodeHerderSearch⌘KRequest access →

Who acts next

Read who must act next on a task, where the web app shows it, and what to do for each kind of wait.

Most open tasks wait on something. When a task waits, CodeHerder works out what it waits on and who must act next, so you can tell at a glance whether a task needs you or is simply in progress. This page explains that answer, where you see it, and what each wait means.

The five answers

The answer is always from your point of view. The same task can read You for an admin and Someone else for a teammate.

Answer What it means
You You can clear the wait now. Open the task and act.
Someone else A person other than you must act. The row names who.
Agent An agent holds the task. It is working, or it waits for an agent to start.
System CodeHerder recovers the wait by itself. You do nothing. Some rows show when.
Done The task finished. It waits on no one.

Where you see it

  • My work, In flight. Each row has a bar that splits the tasks under it by these answers. A Waiting: line under the bar shows the most urgent wait in the tree. Expand a row to see every task under it. See My work.
  • Expanded rows in In flight. Each task shows a badge with its answer. A Someone else badge also names the person. A System badge shows Expected with a time when CodeHerder knows when the wait should clear. A line of text gives the reason.
  • The Tasks list. Hover the Stage control on a row. The tooltip reads “Waiting on” followed by who acts and the reason. A task that waits on no one has no “Waiting on” text. See Finding and tracking your work.

When a task has several waits, the most urgent one shows. A wait for you comes first, then one for someone else, then System, then Agent. So a task can read You while an agent also works on it.

The Done answer only appears in the bar, as the count of finished tasks. A finished task shows no wait. The bar counts the tasks under a top-level task, not the top-level task itself. The Waiting: line includes the top-level task.

What each wait means

What the reason says Who acts What to do
An agent asked a question, or needs input The person named on the question. If none, a workspace admin. Answer it. See When an agent needs your input.
A blocker offers option buttons The person who can resolve it. Pick an option. See Blockers that ask you to choose.
The task waits for approval to move to a stage The named approver. Approve or reject. See Approvals and staying in control.
A network access request waits A workspace admin or owner. Decide the request. See Network access approvals.
A change to managed settings waits A workspace admin. Decide the request. See Approving your organization’s Claude settings.
A plugin marketplace waits for approval A workspace admin. Approve or reject it. See When a task says “Repo config not trusted”.
An admin rejected a plugin marketplace Someone else. The row names the repository. Nothing to approve again. The task waits until that repository stops enabling the marketplace.
A merge request conflicts or was closed A workspace admin. Fix the conflict or decide what happens next. See Waiting for a person to merge.
A pull request waits for a review The people named below. Review it on the git host.
An agent released with nothing to do, or another blocker waits on a person The person who can resolve it. Comment or answer, or resolve the blocker. See Waiting for new input and Blockers and blocked tasks.
CodeHerder refuses to start a session and a person must fix the cause A workspace admin. Read the reason on the task. See Why isn’t my task moving?.
CodeHerder refuses to start a session and retries on its own System. The row can show when. Wait.
The task waits on another task, a git host rate limit, a device with no free capacity, its children or a merge request System. Wait. See Blockers and blocked tasks.
The task stalled and no session runs it System. Read the stalled-task steps in Why isn’t my task moving?.
An agent works on the task Agent. Wait. You can follow the session. See Following a live agent session.
The task waits for an agent to start Agent. Wait. If it stays this way, see Why isn’t my task moving?.

A pull request that waits for a review

A task shows this wait when its checks passed and the git host holds the pull request for a human review. Who acts depends on what the host knows:

  • The host lists requested reviewers. If you are one of them, the answer is You. For everyone else it is Someone else, and the row shows the reviewers’ names.
  • The host lists no reviewers. The person who filed the task and the workspace admins can act. Everyone else sees Someone else. If you wrote the pull request and the host does not let you approve your own work, you also read Someone else.

CodeHerder matches you to a reviewer only when it has confirmed your login on the git host. Until then, you read Someone else even if you are on the list.

Last updated

Try it on one repository for two weeks.

File a task. An agent builds it. A person reads every request. You see the cost of each task.

Try "pricing", "connect a device", or "who reviews the code"

↑↓ move · ↵ open · esc close