{"version":"2.1.234","anchor":"permission-grants-no-longer-get-dropped-in-background-and-sd","canonical_anchor":"permission-grants-no-longer-get-dropped-in-background-and-sd","heading":"Permission grants no longer get dropped in background and SDK sessions","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/permission-grants-no-longer-get-dropped-in-background-and-sd","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Permission grants no longer get dropped in background and SDK sessions\n\nPermission grants from hooks or SDK sessions no longer silently vanish in background agents.\n\n**What**\n\nPermission 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.\n\n**Details**\n\n- A helper builds both setters from a single updater for callers that do not care about the distinction.\n\n**Evidence**\n\n`setSessionToolPermissionContext`\n\n- Area: Permissions\n- Names: `updatedPermissions`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}