{"version":"2.1.300","anchor":"background-bash-tool-result-tells-model-not-to-poll-output-f","canonical_anchor":"background-bash-tool-result-tells-model-not-to-poll-output-f","heading":"Background commands now tell Claude to wait instead of checking the output","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/background-bash-tool-result-tells-model-not-to-poll-output-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Background commands now tell Claude to wait instead of checking the output\n\nWhen a command runs in the background, Claude Code now tells Claude it will be notified and should not keep checking the output file\n\n**Unclear.** It is not clear what decides whether the new wording is used, so it may not apply to every account or model.\n\n**What**\n\nClaude Code can run a shell command in the background, so Claude can keep working while it runs. When it does, it tells Claude about it in the tool result, which is the reply Claude gets back after asking to run something. That reply now says Claude will be notified when the command finishes, and should not keep checking the output file or pause to wait.\n\nIt also tells Claude to read the output file only:\n\n- when you ask how the command is getting on\n\n- when Claude needs a line the command prints before it can carry on, such as a server's ready line or its port\n\nBefore, the reply said Claude would be notified, and told it how to read the file to check on progress. The new wording is used only when the command did not time out, the turn was not stopped, and the reply is not being sent as a message or a final response.\n\n**Why**\n\nClaude should spend less effort repeatedly checking on background commands and wait for the notice that they are done instead.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}