execution_status
Check a run's progress and health: weighted completion, blockers, checks, ETA, budget, runner health, and GitHub sync; inspect tasks, escalations, events, or restart a lost runner.
Instructions
How a heads-down run is doing. Without execution_id: every run with its status. With one, view summary (default) gives weighted completion (accepted 1, submitted 0.8, otherwise the worker's percent or 0.4), blockers, the latest checks, a rough ETA, the budget, runner health, the dashboard URL and GitHub sync health; tasks, escalations, events (since_seq, limit), budget and context are the other views. focus answers questions such as "how close is the nav?": fuzzy words and prefixes matched against task ids, titles, teams, paths and interface names ("nav" finds build-nav-bar and src/components/nav/**); an escalation id as focus picks that escalation for view context. view context returns a redacted bundle (no chat, no secrets) to pass to a format at the table. Restarts the runner of a live run that lost it.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "execution_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| view | No | summary (default), tasks, escalations, events, budget or context. | |
| focus | No | What the human asked about, in their words ("the nav", "api client", a task id, or an escalation id). | |
| limit | No | How many runs, tasks, escalations or events (default 20 runs, 50 otherwise). | |
| since_seq | No | view events: start after this sequence number (default: the latest limit events). | |
| execution_id | No | The heads-down run (exe-…), as execute or execution_status returned it. |