Unclear The finding does not say what consumes this event list or what user-visible behavior, if any, depends on it.
A second, larger internal list of UI and agent events that Claude Code tracks now includes ui.message, joining ui.render, ui.resolve, ui.press, ui.input, and ui.select.
This is internal plumbing that expands the set of events the app can recognize and react to. It does not by itself change what you see, but it lays groundwork for features that need to respond to message-related UI activity.
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.
| `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/interface see the edit
The finding does not say what consumes this event list or what user-visible behavior, if any, depends on it.
A small documentation edit on Draw in the interface with a mod touched a line naming ui.message after this was published.