{"version":"2.1.314","anchor":"background-task-result-wording-for-a-new-mode","canonical_anchor":"background-task-result-wording-for-a-new-mode","heading":"Background task results can arrive between tool calls","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/background-task-result-wording-for-a-new-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Background task results can arrive between tool calls\n\nIn some cases Claude is now told a background task's result arrives between its tool calls, and to wait with one foreground shell command if it needs it\n\n**Unclear.** The condition that selects the new wording is not stated.\n\n**What**\n\nWhen Claude starts a background task (work that keeps running while Claude does other things), it gets a message about how the result will reach it. Under a certain condition, that message now says the result is delivered between its tool calls (each action Claude takes, such as running a command). It adds that if Claude needs the result before replying, it should wait for it with one shell command run in the foreground. Before, the message said the result arrives automatically and told Claude to end its turn.\n\n**Why**\n\nThis changes how Claude waits for background work, so in this case it may keep working or wait in place instead of ending its reply.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}