Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.265 ·

--system-prompt-snapshot now defaults on universally, not just for the built-in prompt

--system-prompt-snapshot's documented default is now described as always-on, not just for the built-in prompt

TierUse it nowhow much it should matter to you
Useful3my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaSystem Promptwhat it touches
KindImprovementsin v2.1.265,
Use it now Notable

--system-prompt-snapshot's documented default is now described as always-on, not just for the built-in prompt

What

The help text for --system-prompt-snapshot now describes the setting as on by default in all cases, rather than only by default for the built-in system prompt (previously, using --system-prompt or --append-system-prompt turned snapshotting off automatically). With the default on, the system prompt - including any text passed via --system-prompt or --append-system-prompt - is rendered once on the conversation's first request, and every later request or resume reuses that exact recorded version, even if a later launch passes different prompt text, until the conversation compacts (summarizes and trims its history).

Relatedly, when snapshotting is on, a set_model system-prompt override now takes effect at the next compaction rather than at the next turn.

Why

This means custom system prompts set via --system-prompt or --append-system-prompt are now also locked in from the first request by default, so changing that text on a later launch of the same conversation won't retroactively change what's already been recorded - only a fresh conversation or a compaction will pick up new text.

See this entry in the whole of v2.1.265 →

Feedback