You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Bug FixesKind: in v2.1.234,
What probably matters to youSection of the release
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.
