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.257 ·

History purge now uses a lock and detects lock compromise

History purges take a lock and refuse the rewrite if another process disturbs it mid-run.

TierYou'll noticehow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaData Retentionwhat it touches
KindBug Fixesin v2.1.257,
You'll notice

History purges take a lock and refuse the rewrite if another process disturbs it mid-run.

History purge and rewrite operations now acquire a lock before running, and detect if another process disturbs it mid-rewrite. If the lock is compromised, the rewrite is refused and reported as History purge lock compromised or History purge (--all) lock compromised.

Read from
Names in the bundle--all
Since it was published

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 since A small documentation edit on Fullscreen rendering touched a line naming --all after this was published. * Rules you passed with [`--allowed-tools` or `--disallowed-tools`](/docs/en/cli-reference#cli-flags), and your `--agent`, `--agents`, `--append-system-prompt`, and `--system-prompt-snapshot` flags fullscreen see the edit
Confirmed since Anthropic's documentation has since written up --all, on Plugins reference. | `-a, --all` | Disable all enabled plugins. Can't be combined with `--scope` | | plugins-reference see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --all, on Plugins reference.

See this entry in the whole of v2.1.257 →

Feedback