{"version":"2.1.233","anchor":"permission-and-dialog-dispatchers-are-now-long-lived-objects","canonical_anchor":"permission-and-dialog-dispatchers-are-now-long-lived-objects","heading":"Permission and dialog dispatchers are now long-lived objects","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/permission-and-dialog-dispatchers-are-now-long-lived-objects","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Permission and dialog dispatchers are now long-lived objects\n\nPermission and dialog prompts can no longer act on stale theme or permission settings.\n\n**What**\n\nThe code that routes tool-permission and user-dialog requests became two objects kept for the session rather than callbacks rebuilt on every render, so it can no longer act on a stale view of the theme, tool registry or permission settings. The same responses are still sent, including the \"User aborted\" deny and the deny on unmount.\n\n**Evidence**\n\n`Permission dispatcher unmounted`\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 2\/5"}