{"version":"2.1.311","anchor":"background-agent-recovery-notices-no-longer-force-a-model-tu","canonical_anchor":"background-agent-recovery-notices-no-longer-force-a-model-tu","heading":"Notices about recovered background agents can now prompt Claude in some cases","tier":"notice","area":"Background Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/background-agent-recovery-notices-no-longer-force-a-model-tu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Notices about recovered background agents can now prompt Claude in some cases\n\nNotices about background agents that finished or failed to restart across a session can now, in some cases, prompt Claude to respond\n\n**Unclear.** Which situations make these notices prompt Claude, rather than stay silent, is not stated.\n\n**What**\n\nA background agent is a helper task that keeps working while you do other things. When you return to an earlier session, Claude Code can show two notices about such agents: one when an agent finished before the previous session ended but its result was never reported, and one when an agent couldn't be restarted.\n\nBefore, these notices never started a new reply from Claude. In some cases they now can.\n\n**Why**\n\nWhen you resume a session, Claude may react to a recovered agent's result right away instead of waiting for your next message.\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}