{"version":"2.1.301","anchor":"bash-tool-result-can-carry-an-explicit-background-output-pat","canonical_anchor":"bash-tool-result-can-carry-an-explicit-background-output-pat","heading":"Background shell commands can report a different output file location","tier":"notice","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/bash-tool-result-can-carry-an-explicit-background-output-pat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Background shell commands can report a different output file location\n\nWhen Claude runs a shell command in the background, Claude Code can now point Claude at a specific output file instead of the default location\n\n**Unclear.** It is not stated what causes background shells to be kept track of separately, so when the new output path applies is unknown.\n\n**What**\n\nThe Bash tool is how Claude runs shell commands. A command can run \"in the background\", meaning it keeps going while Claude does other work and writes what it prints to a file. Claude Code then tells Claude where that file is so it can read it later.\n\nThat location used to always come from the background task's ID. The result of a Bash call can now carry its own output path instead. Claude Code uses that path, when present, to tell Claude where the task's output is. The path is only set in sessions where background shells are being kept track of separately.\n\n**Why**\n\nThis changes where Claude is told to look for the output of a background command, so it reads the right file in setups where background shells are handled elsewhere.\n\n- Area: Background Shells\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}