Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.307 ·

Auto mode filters MCP allow rules and caps the allow-rule list

Auto mode now trims MCP tool allow rules, removes duplicates and caps the list before sending it to the permission classifier

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

Unclear What makes Claude Code send this value, and how it changes matching of MCP allow rules, is not stated.

What

Auto mode lets Claude Code decide on its own whether to run a tool, using a classifier, a server-side check that judges each action. Allow rules are permissions you have set that pre-approve certain tools. MCP tools are tools supplied by outside servers you connect to Claude Code.

  • Auto mode now drops bare MCP tool allow rules that would not be auto-approved anyway.
  • It removes duplicate allow rules and caps how many are sent.
  • When filtering succeeds, it sends a new optional true-or-false field, mcp_allow_rules_exact, to the classifier. The field is sent only when true.
  • If filtering fails, the rules are sent unfiltered and without mcp_allow_rules_exact, and a message says so.
  • Claude Code's internal report of incomplete auto mode context now also counts allow rules: the total, repeats, distinct rules and the cap.

Why

The classifier receives a shorter, cleaner list of rules. MCP allow rules may be matched differently as a result, so watch whether MCP tools you rely on are approved as before.

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 doubtWhat makes Claude Code send this value, and how it changes matching of MCP allow rules, is not stated.

See this entry in the whole of v2.1.307 →

Feedback