What
A new check runs when a hooks module (a script that registers hook handlers) subscribes to the ui.render event with a matcher (a filter deciding which calls the hook applies to). If there's advice available about that matcher, Claude Code now logs a warning at startup showing the matcher's contents.
Why
This surfaces potential problems with a hook's ui.render matcher up front, rather than leaving the author to discover an issue only when the hook misbehaves.
Names in the bundleui.render
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up ui.render, on Draw in the interface with a mod.
on('ui.render', { component: 'Spinner' }, async ($, e, next) => {plugins/mods/interface see the edit
Added since
A small documentation edit on Mods reference touched a line naming ui.render after this was published.
Elements are the building blocks of a tree a `ui.render` hook returns, and you get them from `$.ui.resolve(e)`. [Build a tree from elements](/docs/en/plugins/mods/interface#build-a-tree-from-elements) shows the common ones with how the ter…plugins/mods/reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Mods reference touched a line naming ui.render after this was published.