{"version":"2.1.275","anchor":"new-plugin-api-method-uipanes-with-no-permission-check-wir","canonical_anchor":"new-plugin-api-method-uipanes-with-no-permission-check-wir","heading":"New plugin API method ui.panes with no permission check, wired end-to-end but never called by anything else in the bundle","tier":"soon","area":"Plugin API","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-plugin-api-method-uipanes-with-no-permission-check-wir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### New plugin API method ui.panes with no permission check, wired end-to-end but never called by anything else in the bundle\n\nNew plugin API method ui.panes lets plugins list their own UI panels, with no permission check\n\n**Unclear.** The finding shows the method wired into the dispatch table and SDK but not called elsewhere, so what a plugin author would use it for in practice is unclear.\n\n**What**\n\nA new method, `ui.panes`, was added to the plugin runtime API. It returns the list of UI panes (panels) that belong to the calling plugin, including each pane's id, title, and whether it's shown, focused, or placed. The plugin SDK now exposes this as `panes()`. Unlike the similar `ui.open`, `ui.close`, `ui.scroll`, and `ui.focus` methods, `ui.panes` has no permission check attached to it.\n\n**Why**\n\nThis gives plugin authors a way to inspect their own panes' state, though nothing else in Claude Code currently calls it, so its practical use isn't yet visible.\n\n- Area: Plugin API\n- Names: `ui.panes`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}