{"version":"2.1.287","anchor":"background-agent-blocked-status-no-longer-sticks-on-bridge-e","canonical_anchor":"background-agent-blocked-status-no-longer-sticks-on-bridge-e","heading":"Background sessions no longer stay stuck as blocked after a question is answered","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/background-agent-blocked-status-no-longer-sticks-on-bridge-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Background sessions no longer stay stuck as blocked after a question is answered\n\nA background session's blocked status now clears when its stored request just repeats text that was already passed along\n\n**What**\n\nA background session is a Claude Code session that keeps working on its own while you do something else. It can be marked as blocked, meaning it is waiting on you, along with a short note of what it needs.\n\nClaude Code now clears an out-of-date blocked status when the stored note matches either of these:\n\n- the text most recently passed along to the session\n\n- the last note passed along to it\n\nA turn with no text also no longer reuses an old note.\n\n**Why**\n\nBackground sessions should stop showing as blocked once you have answered the question they were waiting on.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}