Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

Permission prompts: organization limits act as a floor, and your rejection reason is kept

Organization-limited permission asks are now handled as a floor, and a reason you give when denying a tool call can be passed back

Group of 2 You'll notice Improvements
JSON All of v2.1.323
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release

Unclear It is not clear which permission prompts appear or disappear for a user as a result of this change.

What

Before Claude uses a tool, such as running a command, Claude Code may ask your permission. Auto mode decides some of these for you. This release changes how those asks work:

  • Organization limits: the old check looked at whether an MCP server's effectiveMaxPermission was "ask". MCP servers are add-ons that give Claude extra tools. The new check stops early when the ask carries an organization limit (orgLimit), so a ceiling set by your organization still forces a prompt.
  • Your feedback on a denial: when you reject a tool call, the text you typed can now be carried in the deny result as userFeedback. Before, deny results had no such field.
  • Consent words: some ask results, and the browser floor-block code, now clear consentWordsOnRecord.

Why

Your organization's permission limits keep producing a prompt even in auto mode. A reason you type when rejecting a tool call can now reach Claude.

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 doubtIt is not clear which permission prompts appear or disappear for a user as a result of this change.

See this entry in the whole of v2.1.323 →

Feedback