Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PluginsArea: what it touches
Internal ChangesKind: in v2.1.268,
Internal ChangesSection of the release
Unclear What specific desktop client or surface consumes these dispatched events isn't detailed in the evidence.
What
Two new internal functions dispatch plugin-authored UI events, including ui.message and press/input/select events, to a message target marked as surface: "desktop". Before dispatching, they check whether the relevant UI component (Q4.isDrawn) is actually drawn, and log a message noting 'nothing ran' when it isn't.
Why
This appears to add the plumbing needed for plugin-driven UI events to reach a desktop client interface, separate from the terminal-based UI, though what desktop surface consumes these events isn't detailed in the evidence.
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.
Added sinceA small documentation edit on Draw in the interface with a mod touched a line naming ui.message after this was published.| `Client` | A region drawn by a second file of yours, for animation and pointer input. That file gets no mods API. It reaches your hooks by posting data, which arrives as a `ui.message` event. If it fails to load, draw, or run, your hooks…plugins/mods/interfacesee the edit
Confirmed sinceAnthropic's documentation has since written up ui.press, on Draw in the interface with a mod.A test presses or types into a control by its `key`, so give each control one. Each use of a control also fires [`ui.press`, `ui.input`, or `ui.select`](/docs/en/plugins/mods/reference#interface) with the `key` in `e.element`, and another …plugins/mods/interfacesee the edit
Confirmed sinceAnthropic's documentation has since written up ui.select, on Draw in the interface with a mod.A test presses or types into a control by its `key`, so give each control one. Each use of a control also fires [`ui.press`, `ui.input`, or `ui.select`](/docs/en/plugins/mods/reference#interface) with the `key` in `e.element`, and another …plugins/mods/interfacesee the edit
Confirmed sinceAnthropic's documentation has since written up ui.input, on Draw in the interface with a mod.A test presses or types into a control by its `key`, so give each control one. Each use of a control also fires [`ui.press`, `ui.input`, or `ui.select`](/docs/en/plugins/mods/reference#interface) with the `key` in `e.element`, and another …plugins/mods/interfacesee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat specific desktop client or surface consumes these dispatched events isn't detailed in the evidence.
Anthropic's documentation agreesAnthropic's documentation has since written up ui.input, on Draw in the interface with a mod.
