{"version":"2.1.295","anchor":"background-bash-prompt-has-a-variant-without-the-notificatio","canonical_anchor":"background-bash-prompt-has-a-variant-without-the-notificatio","heading":"Bash and PowerShell guidance on background commands now depends on a check","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/background-bash-prompt-has-a-variant-without-the-notificatio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Bash and PowerShell guidance on background commands now depends on a check\n\nThe instructions Claude gets for Bash and PowerShell now leave out some background-run advice when an internal check says so\n\n**Unclear.** It is not stated what condition decides which version of the description Claude sees.\n\n**What**\n\nClaude gets written instructions for each tool it can use. Two of them, for running commands in the background with `run_in_background`, now change depending on a check:\n\n- Bash: when the check is false, the description of `run_in_background` no longer promises you will be notified when the command finishes. It ends with a different sentence instead: `Only use this if you don't need the result immediately.`\n\n- PowerShell: the advice about `Start-Sleep`, `run_in_background` and polling is only included when a check for background support passes. Before, it was always included.\n\n**Why**\n\nClaude should stop being told to rely on background running or completion notices in setups where they do not apply.\n\n- Area: Elsewhere\n- Names: `run_in_background`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}