Under the hood
Plugin button presses can now be intercepted by a runner override, and plugins gain a 'core' tier label
What
When a plugin UI button or press is handled, Claude Code now first checks for a runner-level override before falling back to the plugin's own press handler. Separately, plugin descriptors and loaded module listings now carry a tier field, with 'core' as one observed value.
Why
The override mechanism suggests something outside a plugin's own code can now intervene in how its button presses are handled, and the new tier field suggests plugins are now categorized, for example distinguishing built-in 'core' plugins from others, though the finding doesn't say what uses this distinction.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What consumes the `tier` field or the runner override, and what other tier values exist besides 'core', is not stated.