{"version":"2.1.292","anchor":"completed-local-agents-can-show-as-waiting-rather-than-do","canonical_anchor":"completed-local-agents-can-show-as-waiting-rather-than-do","heading":"Some finished background agents now show as 'waiting' instead of 'done'","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/completed-local-agents-can-show-as-waiting-rather-than-do","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Some finished background agents now show as 'waiting' instead of 'done'\n\nIn the task list, a finished local agent can now show a 'waiting' status, and is not counted as completed\n\n**Unclear.** It is not clear what condition makes a finished agent show as waiting.\n\n**What**\n\nIn the task list, which shows agents (helpers Claude runs alongside your conversation) working in the background, a finished local agent used to show as \"parked\" or \"done\".\n\nNow, under a new condition, a finished local agent shows a \"waiting\" icon and label instead, and is not counted as completed. Agents that were set aside still show \"parked\".\n\n**Why**\n\nThe status you see in the background-tasks panel can now read \"waiting\" for an agent that would earlier have read \"done\".\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}