{"version":"2.1.281","anchor":"no-session-persistence-check-moved-earlier-and-now-applied","canonical_anchor":"no-session-persistence-check-moved-earlier-and-now-applied","heading":"--no-session-persistence check moved earlier and now applied immediately","tier":"use","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/no-session-persistence-check-moved-earlier-and-now-applied","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### --no-session-persistence check moved earlier and now applied immediately\n\n`--no-session-persistence` is checked earlier and takes effect at once, and `--managed-settings` and setting sources are passed to child processes\n\n**Unclear.** The finding does not say what condition decides whether the `agent` and `agents` options are passed to the child process.\n\n**What**\n\n`--no-session-persistence` stops sessions from being saved to disk, so they cannot be resumed later. It still only works together with `--print`, which runs Claude Code once without the interactive screen. The check that enforces this now runs earlier, before the SDK and remote setup. When the flag is accepted, saving is switched off straight away.\n\nOther startup changes in the same area:\n\n- `--managed-settings` and the setting sources are now passed on to the child process that Claude Code starts\n\n- The `agent` and `agents` options are passed on only when a certain condition holds\n\n**Why**\n\nBecause saving is switched off before the rest of setup runs, nothing set up earlier gets a chance to save the session. Managed settings and your chosen setting sources now also reach the child process.\n\n- Area: Sessions\n- Names: `--no-session-persistence`, `--print`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}