{"version":"2.1.311","anchor":"background-tool-run-output-kept-on-disk","canonical_anchor":"background-tool-run-output-kept-on-disk","heading":"Monitor commands now keep their output in a file","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/background-tool-run-output-kept-on-disk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Monitor commands now keep their output in a file\n\nBackground monitor commands now save their output to disk and return its location instead of only the last lines of errors\n\n**Unclear.** It is unclear whether you can see or open the saved output yourself.\n\n**What**\n\nWhen Claude Code runs a monitor command, one that runs in the background and watches something, it used to return only the last lines of error output and then delete the output file. It now writes the output to disk, returns where that file is, and records whether the command exited or was stopped.\n\n**Why**\n\nThe full output of a monitor run can be read later instead of being lost.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}