{"version":"2.1.290","anchor":"bash-tool-a-pasted-multi-pipeline-or-sandbox-hint-is-reword","canonical_anchor":"bash-tool-a-pasted-multi-pipeline-or-sandbox-hint-is-reword","heading":"Hint about remote background commands no longer says the output shows how they ended","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bash-tool-a-pasted-multi-pipeline-or-sandbox-hint-is-reword","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Hint about remote background commands no longer says the output shows how they ended\n\nA hint about commands running in the background remotely now says their output file shows what printed, not whether they are still running\n\n**What**\n\nWhen the shell command tool runs a command in the background on a remote machine, Claude Code gives a hint about how to check on it. That hint used to say the command was over if its output file ended with a line saying how it ended. It now says the output file shows what the command has printed, not whether it is still running. This applies when a fallback path is used.\n\n**Why**\n\nA command can print a line that looks like an ending message, so the old advice could be fooled. The new wording avoids relying on it.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}