{"version":"2.1.280","anchor":"diskless-sessions-get-a-synthetic-task-output-root-and-disab","canonical_anchor":"diskless-sessions-get-a-synthetic-task-output-root-and-disab","heading":"Diskless sessions get a synthetic task-output root and disable shell entirely","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/diskless-sessions-get-a-synthetic-task-output-root-and-disab","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Diskless sessions get a synthetic task-output root and disable shell entirely\n\nDiskless sessions now use a synthetic output path and can't run shell commands at all\n\n**What**\n\nWhen a session runs in 'diskless' mode (without a real disk to write to), background task output now goes to a synthetic placeholder path, `\/nonexistent\/claude-code-diskless`. Separately, any attempt to run a shell command in a diskless session now fails immediately with the reason `diskless_no_shell` instead of attempting to execute it.\n\n**Why**\n\nThis makes it explicit and immediate that shell commands can't run without a disk, rather than letting a command attempt fail in a confusing way partway through.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}