{"version":"2.1.281","anchor":"diskless-sessions-task-output-paths-now-throw-instead-of-po","canonical_anchor":"diskless-sessions-task-output-paths-now-throw-instead-of-po","heading":"Diskless sessions: task output paths now throw instead of pointing at a placeholder directory","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/diskless-sessions-task-output-paths-now-throw-instead-of-po","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Diskless sessions: task output paths now throw instead of pointing at a placeholder directory\n\nIn diskless sessions, asking for a task's output file now fails with an error instead of returning a fake path\n\n**Unclear.** The finding does not say what a user sees when this error occurs.\n\n**What**\n\nA diskless session is one that does not write files to disk. Previously, asking for the folder a task's output goes to returned a placeholder path in such a session, which was `\/nonexistent\/claude-code-diskless` in v2.1.280. Now asking for a task's output file path fails with the error \"Task output has no file in a diskless session\". Reading an output path returns nothing.\n\n**Why**\n\nCode can no longer quietly use a path that does not exist. The problem shows up as a clear error instead.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}