{"version":"2.1.227","anchor":"bash-results-say-when-a-background-command-dies-with-its-age","canonical_anchor":"bash-results-say-when-a-background-command-dies-with-its-age","heading":"Bash results say when a background command dies with its agent","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/bash-results-say-when-a-background-command-dies-with-its-age","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Bash results say when a background command dies with its agent\n\nBash results now flag a background command that dies when its subagent finishes.\n\n**What**\n\nA backgrounded command started by a synchronous subagent is now marked in the tool result, because it gets killed when that subagent gives its final response. The field is absent when the command outlives its starter, as in the main loop or an async subagent.\n\n**Evidence**\n\n`backgroundEndsWithFinalResponse`\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}