{"version":"2.1.232","anchor":"clearer-notice-when-a-background-agent-could-not-be-restarte","canonical_anchor":"clearer-notice-when-a-background-agent-could-not-be-restarte","heading":"Clearer notice when a background agent could not be restarted","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/clearer-notice-when-a-background-agent-could-not-be-restarte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Clearer notice when a background agent could not be restarted\n\nFailed agent restarts now give advice matching how the agent was launched.\n\n**What**\n\nThe message for an agent that failed to auto-restart now depends on how it was launched: agents started via web fetch are told SendMessage is the only way to get the report, while others keep the advice to check the worktree or output file for partial work.\n\n**Evidence**\n\n`, which is the only way to get its report.`\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}