You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Background ShellsArea: what it touches
ImprovementsKind: in v2.1.301,
ImprovementsSection of the release
Unclear It is not stated what causes background shells to be kept track of separately, so when the new output path applies is unknown.
What
The 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.
That 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.
Why
This 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not stated what causes background shells to be kept track of separately, so when the new output path applies is unknown.
