{"version":"2.1.323","anchor":"auto-mode-denials-carry-user-feedback-consent-words-field-c","canonical_anchor":"auto-mode-and-permission-code-treats-org-limited-ask-as-a-fl","heading":"Permission prompts: organization limits act as a floor, and your rejection reason is kept","tier":"notice","area":"Permissions","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/auto-mode-denials-carry-user-feedback-consent-words-field-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Permission prompts: organization limits act as a floor, and your rejection reason is kept\n\nOrganization-limited permission asks are now handled as a floor, and a reason you give when denying a tool call can be passed back\n\n**What**\n\nBefore 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:\n\n- 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.\n\n- 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.\n\n- Consent words: some ask results, and the browser floor-block code, now clear `consentWordsOnRecord`.\n\n**Why**\n\nYour 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.\n\n- Area: Permissions\n- Names: `userFeedback`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}