Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.235 Home All releases olderv2.1.234 v2.1.236newer
Claude Code v2.1.235

Permission rules can only be written from a dialog row the dialog itself created

You'll notice
Useful4 Signal3
Permissions

Persistent permission rules only save when the dialog itself built the option; untrusted text hides them entirely.

What

Bash prefix and exact, Chrome host, Skill exact and prefix, plan-mode keep-context and MCP elicitation prompts now refuse to persist a permission rule unless the option came from the dialog's own constructor, falling back to a one-time allow that writes nothing. Untrusted text that cannot be displayed safely suppresses the persistent options outright. This applies to everyone on this build.

Details
  • Options are produced by a constructor guarded by a private token; combining or applying rows checks that provenance first.
  • MCP server and tool names, elicitation URLs, commands, skill and cell names and question labels are rendered through a sanitizer that can mark a value withheld, showing "approval withheld; one-time options only".
  • When a value is withheld, the URL elicitation dialog also starts on "decline" and refuses to open the URL.
Evidence

combineRows accepts only constructor-produced ConsentRows

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.235 →