Monitor workflows and agents
Follow agent work from Workflows, the Work queue, the linked work item, or an agent's details page.
Choose the right view
| View | What to inspect |
|---|---|
| Workflows overview | Definitions, online agents, recent sessions, and workflow runs. |
| Workflow Runs tab | Step attempts, routes, review gates, stalls, branches, and terminal outcomes for one definition. |
| Work queue | Up to ten queued, active, awaiting-input, and recently finished sessions without leaving the current page. The badge counts queued and active sessions. |
| Session details | Claim owner, activity timeline, capabilities, provider metadata, token usage, worktree, errors, and available actions. |
| Agent details | Online, stale, or offline health; settings; sessions targeted to that agent; and local start or restart controls. |
| Linked work item | The specification, workflow documents, comments, branch or PR/MR, and final delivery context. |
Open a session to tell queued work from an active claim. Inspect the status, latest activity, and agent heartbeat before choosing a recovery action.
When a tool or integration was unavailable, the session's Capabilities tab shows why. Agent capabilities explains its Managed, Observed local, and Excluded sections and the retry mismatch notice.
Session states
| State | Meaning |
|---|---|
queued | Waiting for an eligible agent to claim it. |
pending | Accepted but not ready to execute. |
active | An agent holds the claim and is executing. |
awaiting_input | The agent paused for a reply. Choose Resume and provide the requested input. |
complete | The agent reported success. Review the result before merging or closing the work. |
error | Execution failed. Inspect the error and activity before retrying. |
stale | Heartbeats or the claim expired. The previous agent may reclaim it, or you can create a replacement run. |
cancelled | A user or system cancelled the session. |
Workflow runs separately use not_started, running, waiting_for_review, stalled, completed, cancelled, and failed. A session can finish while its workflow waits at the next step or review gate.
Actions
| Action | When it appears | Result |
|---|---|---|
| Resume | An agent session is awaiting_input | Queues one reply for the owning online agent and refreshes the active claim lease. |
| Resume on a workflow run | A stalled run exhausted the current step's pass limit | Skips the exhausted step attempt and follows that step's configured route. |
| Try again | A session is stale, errored, cancelled, queued, or pending; completed sessions can also be retried | Creates a replacement session with the same work, prompt, agent profile, and target. Failed or unstarted source sessions are archived after replacement. |
| Archive | A session is complete, error, cancelled, or stale | Hides it from queue and session lists without changing the work item or its activity history. |
| Cancel | A session or workflow run is still active | Stops the current execution path and records a cancelled outcome. |
| Open in Codex | A Codex local session has a recorded thread ID | Opens the recorded Codex thread. |
| Open in Claude Code | A Claude Code local run is complete or errored and has a session ID | Resumes that session in the task workspace folder. |
Before you Resume a pass-limit stall, inspect the stalled reason, current attempt, and route destination.
For an awaiting-input session, the reply can contain up to 20,000 characters. Only one reply can be pending, and the owning agent must be online. The agent consumes the input on its next poll without creating a new claim.
Review gates
Human review steps appear in Work Inbox and the workflow run. Approve continues forward, feedback returns to the configured earlier step, reject follows the explicit reject route, and reassignment changes the reviewer without advancing the run.
Agent review steps make the same decision, and a missing verdict stalls the workflow. Activity text alone is not a verdict, and a session that reported a verdict still needs a terminal state to be complete.
Activities and metadata
Activities explain meaningful progress. Common entries include progress, plan_updated, external_url_updated, awaiting_input, user_resume_input, completed, failed, and policy_decision. Heartbeats indicate health and should not be read as progress.
Session metadata can include provider thread and process IDs, model and provider, working directory, worktree path, provider status, external URL, and token counts. Session details show total, input, and output token counts after a terminal state when the harness reported them.
Agent health
Local agents heartbeat while their process is running. A missed heartbeat moves the agent through stale and offline health, expires active claims, and can leave sessions stale. Check Desktop ownership, Auto start, agent logs, one agent status, and local resource pressure before replacing the run.
Recently finished sessions remain in Work queue for about eight hours before they age out. Archive removes a finished session immediately; archived sessions cannot be claimed or restored from the dashboard.