{"version":"2.1.282","anchor":"task-output-write-probe-added","canonical_anchor":"task-output-write-probe-added","heading":"Claude Code can check that task output can be written","tier":"internal","area":"Bash Tool","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/task-output-write-probe-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Claude Code can check that task output can be written\n\nA new check writes and deletes a small test file next to a task's output to confirm the location is writable\n\n**Unclear.** Where this check is used is not known.\n\n**What**\n\nClaude Code has a new check for task output locations. It creates a small, uniquely named test file with a `.probe` extension next to where a task writes its output, writes to it, then deletes it. If the delete fails, it logs a message.\n\n**Why**\n\nThis lets a task (work Claude Code runs in the background) find out early that its output location cannot be written to.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}