You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.317,
ImprovementsSection of the release
What
When you leave a session, Claude Code prints a command you can run to pick it up again. That command used to be only claude --resume followed by the session's id, plus --worktree when it applied. It can now also include the flags you launched Claude Code with, such as --settings. A flag (an option typed after claude on the command line) is added when it is short enough or does not contain a file path.
Separately, the way Claude Code saves files gains a create-only mode. Claude Code writes a temporary file first and then moves it into place. In create-only mode it refuses to replace a file that already exists and fails instead.
Why
Running the printed command can now bring back the same settings you started with, not only the conversation. The create-only mode means a save can be made to stop rather than overwrite something already there.
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.
Added sinceA small documentation edit on Best practices for Claude Code touched a line naming --settings after this was published.* `--append-system-prompt`, `--mcp-config`, and `--settings` explicitly pass in what the run *does* need. Hooks you pass with `--settings` [don't run under `--bare`](https://code.claude.com/docs/en/headless#start-faster-with-bare-mode), so…best-practicessee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesA small documentation edit on Best practices for Claude Code touched a line naming --settings after this was published.
Anthropic's release notes agreeImproved the "Resume this session with" hint shown at exit to repeat the flags you launched with (for example --chrome --debug) ahead of…
