Bash no longer suggests backgrounding a long-running command; commands can still end up backgrounded when a turn is aborted.
What's wrong with this entry?
Bash no longer shows the prompt telling you a long-running command can be moved to the background; that plumbing is deleted rather than relocated, going from 14 occurrences in 2.1.246 to none. In its place the tool result gained backgroundedByTurnAbort, documented as true when a plugin's turn abort moved the running command to the background.
- The tool now passes a caller identity into the shell runner.
- The persisted-output path passes the session's storage version through to the directory-ensure call.
- Unconditional; nothing gates it.
@internal True if a plugin's turn abort moved the running command to the background
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Every session now gets the
cdpermission warning in the Bash toolBoth mention bash tool
-
v2.1.234
Command lessons are recorded with the command that produced them
Both mention bash tool
-
v2.1.238
Directory tracking for backgrounded commands no longer breaks early
Both mention bash tool