{"version":"2.1.304","anchor":"diskless-sessions-refuse-disk-backed-features","canonical_anchor":"diskless-sessions-refuse-disk-backed-features","heading":"Sessions with no disk skip features that need to save files","tier":"internal","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/diskless-sessions-refuse-disk-backed-features","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Sessions with no disk skip features that need to save files\n\nIn a session running with no disk, Claude Code skips feedback drafts, the changelog cache, teammate spawning and the plugin relevance scan\n\n**Unclear.** What starts a session with no disk, and whether a user can choose it, is not stated.\n\n**What**\n\nClaude Code can now run a session with no disk, meaning it does not save files to your computer. In that kind of session, these features are skipped or refused:\n\n- Feedback drafts are not saved.\n\n- The changelog cache is not used.\n\n- Starting a teammate, a helper agent that works alongside the main session, is refused.\n\n- The scan that checks which plugins are relevant is skipped.\n\nThe message Claude gets when a Monitor watch runs out also reads differently in this mode, warning that after it replies a new watch may stop within a minute.\n\n**Why**\n\nClaude Code can now run where there is no disk to write to, and features that depend on one step aside instead of failing.\n\n- Area: Diskless Sessions\n- Tier: Under the hood\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}