Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

Permission questions from plugin-started runs should hide the always-allow option

For permission questions from a run a plugin started, Claude Code saves no rule from your answer, and hosts are told to hide the always-allow choice

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

Claude Code can send permission questions to a host, the program that shows you Claude Code's prompts, such as an app built on the Claude Agent SDK. A question can carry suppress_always_allow_rule, which tells the host not to offer a lasting "always allow" choice.

Its description used to cover one case: whole-tool allow rules broader than the action being asked about. It now also covers questions from a run that a plugin (an add-on package for Claude Code) started. For those, Claude Code saves no rule from your answer, not even for the current session, and the host should hide the option.

Why

Your answer to a question from a plugin-started run only covers that one action, so an "always allow" choice there would promise something Claude Code does not do.

See this entry in the whole of v2.1.317 →

Feedback