{"version":"2.1.259","anchor":"plugin-ui-hooks-can-now-invalidate-on-promptcontext-not-ju","canonical_anchor":"plugin-ui-hooks-can-now-invalidate-on-promptcontext-not-ju","heading":"Plugin UI hooks can now invalidate on prompt.context, not just prompt.section","tier":"use","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/plugin-ui-hooks-can-now-invalidate-on-promptcontext-not-ju","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Plugin UI hooks can now invalidate on prompt.context, not just prompt.section\n\nPlugins can now invalidate prompt.context specifically through ui.invalidate, alongside ui.render and prompt.section.\n\nThe plugin SDK bridge's `ui.invalidate` call now also accepts `\"prompt.context\"` as an event to invalidate, alongside the existing `\"ui.render\"`, `\"prompt.section\"`, and `\"tool.describe\"`, letting plugins force a refresh of that section specifically.\n\n- Area: Plugin Hooks\n- Names: `prompt.context`, `ui.invalidate`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}