What probably matters to youSection of the release
What
--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.
Other startup changes in the same area:
--managed-settings and the setting sources are now passed on to the child process that Claude Code starts
The agent and agents options are passed on only when a certain condition holds
Why
Because 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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up --print, on Error reference.| `Error: --agents takes a JSON object, or a file path only with --print (-p)` | [Command-line errors](#invalid-agents-configuration) |errorssee the edit
Confirmed sinceAnthropic's documentation has since written up --no-session-persistence, on Connect Claude Code to tools via MCP.If you disable session persistence with [`--no-session-persistence`](/docs/en/cli-reference#cli-flags) or [`CLAUDE_CODE_SKIP_PROMPT_HISTORY`](/docs/en/env-vars), Claude Code writes no image file and Claude receives only the inline copy.mcpsee the edit
Added sinceA small documentation edit on CLI reference touched a line naming --print after this was published.| `--bg`, `--background` | Start the session as a [background agent](/docs/en/agent-view) and return immediately. Prints the session ID and management commands. Combine with `--exec` to run a shell command as a background job instead of a …cli-referencesee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what condition decides whether the `agent` and `agents` options are passed to the child process.
Anthropic's documentation agreesA small documentation edit on CLI reference touched a line naming --print after this was published.
