{"version":"2.1.268","anchor":"background-agent-restart-failure-message-distinguishes-reada","canonical_anchor":"background-agent-status-messages-adapt-when-the-agent-has-no","heading":"Background agent messages now depend on whether its output file can still be read","tier":"notice","area":"Background Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/background-agent-restart-failure-message-distinguishes-reada","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Background agent messages now depend on whether its output file can still be read\n\nClaude Code now tracks whether a background agent's output file is still readable and changes its guidance accordingly\n\n**What**\n\n- A new `canReadOutputFile` flag is now tracked on background\/async agent launches, defaulting to true, and set explicitly in several agent dispatch and relaunch code paths.\n\n- Status and notification messages for a stopped or interrupted background agent now check this flag: when it's false, Claude Code tells you to resume the agent and ask it for a status report, instead of suggesting you check its worktree or output file for partial work.\n\n- The message shown when a background agent from a previous session can't be restarted now also depends on this flag: if the output file can be read, it still suggests checking the worktree\/output; if not, it suggests messaging the agent for a status report instead.\n\n**Why** Not every background agent leaves behind a readable output file. This change makes the guidance Claude Code gives you match what's actually possible, instead of pointing you to a file you can't inspect.\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}