{"version":"2.1.301","anchor":"background-task-exit-state-reporting-reshaped","canonical_anchor":"background-task-exit-state-reporting-reshaped","heading":"Killed background tasks can report that they hit the output limit","tier":"notice","area":"Background Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/background-task-exit-state-reporting-reshaped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Killed background tasks can report that they hit the output limit\n\nA finished background task now reports either its exit code or that it was killed, with an output-limit reason when known\n\n**Unclear.** It is not certain that this reporting belongs to background tasks rather than some other part of Claude Code.\n\n**What**\n\nA background task is a command that keeps running while Claude carries on with other work. How its end is reported has changed. The result is now one of two shapes:\n\n- Exited, with the exit code (the number a program returns when it stops)\n\n- Killed, with the reason `output_limit` when the size of the task's output file is known\n\n**Why**\n\nWhen a task is stopped because it produced too much output, the report can now say so instead of only saying it was killed.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}