{"version":"2.1.289","anchor":"new-plugin-function-hooks-feature-slot-plugin-function-hook","canonical_anchor":"new-plugin-function-hooks-feature-slot-plugin-function-hook","heading":"A new drawing slot for plugin function hooks, plus an interface fault event","tier":"internal","area":"Plugin Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/new-plugin-function-hooks-feature-slot-plugin-function-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### A new drawing slot for plugin function hooks, plus an interface fault event\n\nClaude Code lists a new drawing slot for plugin function hooks and a new interface event for reporting faults\n\n**Unclear.** It is not clear what switches the new drawing slot on, or whether users can reach it at all.\n\n**What**\n\nPlugins are add-ons that extend Claude Code. Some of them supply function hooks, which are pieces of plugin code that Claude Code runs at set moments. Claude Code keeps a list of the moments a plugin function hook can attach to. That list already had slots for when a plugin loads and for when it connects to an MCP server, which is an external tool server. This release adds a new slot named `plugin_function_hooks_draw`.\n\nTwo other changes sit alongside it:\n\n- A new interface event called `ui.fault` joins the list of events the interface can send.\n\n- The existing `ui.scroll` and `ui.focus` events are now handled through a new shared helper.\n\n**Why**\n\nTaken together, these changes point toward plugin hooks that can draw on screen and report faults in the interface. No setting or command for reaching them is described yet, so they do not change anything you can do today.\n\n- Area: Plugin Hooks\n- Names: `plugin_function_hooks_draw`\n- Tier: Under the hood\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}