Unclear The finding does not say what running ui.render inside a drawing context changes for plugin authors.
What
Plugins can draw their own interface elements. When one of these elements is pressed and held, the plugin can now check the value and refuse it, in which case the message is that it does not take that value and nothing ran. These events can also carry a request ID. ui.render now runs inside a drawing context.
Why
A refused value now ends with a clear statement that nothing ran, rather than the element acting on input it cannot use.
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
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what running `ui.render` inside a drawing context changes for plugin authors.
Anthropic's documentation agrees
A small documentation edit on Mods reference touched a line naming ui.render after this was published.