{"version":"2.1.280","anchor":"uiclose-hook-chain-now-fires-plugin-ask-dismissal-even-with","canonical_anchor":"uiclose-hook-chain-now-fires-plugin-ask-dismissal-even-with","heading":"ui.close hook chain now fires plugin-ask dismissal even with no handlers","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/uiclose-hook-chain-now-fires-plugin-ask-dismissal-even-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### ui.close hook chain now fires plugin-ask dismissal even with no handlers\n\nClosing a plugin UI panel now also dismisses any pending 'ask' prompt for it, even with no close handlers set up\n\n**What**\n\nWhen a person (rather than an automated hook chain) closes a plugin's UI panel, and that plugin has no `ui.close` handlers registered to run, Claude Code now also calls a cleanup function that dismisses any pending 'ask' record tied to that plugin's panel, instead of just closing the panel and leaving the pending ask behind.\n\n**Why**\n\nThis prevents a plugin's pending 'ask' prompt from being left dangling after its panel is closed, ensuring the plugin's state stays consistent even when it hasn't defined its own close-handling logic.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}