Follow Discord
Sweep 12 Nov 2026 · 20:38Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.322 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
The last run did not finish v2.1.323 no changelog was produced for this release

Claude Code v2.1.271 ·

New appliesModeDrop: !1 escape hatch for mode-based tool restriction, unused

A new but currently unused appliesModeDrop: false option can bypass mode-based tool restrictions

Under the hood Internal Changes
JSON All of v2.1.271
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.271,
Internal ChangesSection of the release

Unclear The finding doesn't show anything actually setting appliesModeDrop to false, so it's unclear what currently uses this escape hatch.

What

The same tool-restriction logic that decides which tools get cut based on the current mode now has an escape hatch: if a new options field called appliesModeDrop is explicitly set to false, no restriction is applied at all, alongside the existing exemptions for things like plugin_install_diff and plugins_sync.

Why

This adds a way to opt specific cases out of mode-based tool restriction, though nothing yet appears to set this option, so it has no visible effect for users right now.

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 doesn't show anything actually setting `appliesModeDrop` to false, so it's unclear what currently uses this escape hatch.

See this entry in the whole of v2.1.271 →

Feedback