{"version":"2.1.229","anchor":"killed-background-shells-show-a-killed-marker","canonical_anchor":"killed-background-shells-show-a-killed-marker","heading":"Killed background shells show a [killed] marker","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/killed-background-shells-show-a-killed-marker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Killed background shells show a `[killed]` marker\n\nStopping a background shell appends a [killed] marker so truncated logs are obvious.\n\n**What**\n\nStopping a background shell now appends an explicit `[killed]` line to its output, so a truncated log is distinguishable from one that ended on its own. The \"stopped\" event also now includes the path of the output file.\n\n**Evidence**\n\n`[killed]`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}