Source Intelligence
Follow Discord

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.234 Home All releases ←olderv2.1.233 v2.1.235newer→
Claude Code v2.1.234

Permission grants no longer get dropped in background and SDK sessions

You'll notice
Useful4 Signal3
Permissions not in their notes

Permission grants from hooks or SDK sessions no longer silently vanish in background agents.

updatedPermissions
What

Permission changes coming from hooks, a permission-prompt tool or an updatedPermissions response now go through a separate session-level setter as well as the app-wide one. Contexts that intentionally do not share app state, such as background agents and some SDK hosts, pass a no-op for the app setter but still forward the session one, so a granted permission takes effect instead of vanishing.

Details
  • A helper builds both setters from a single updater for callers that do not care about the distinction.
Evidence

setSessionToolPermissionContext

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.234 →