Group of 3 Under the hood
No documentation found
Plugins and hooks gain a session.surfaces (plural) endpoint listing all attached drawing surfaces, plus a matching lifecycle hook event
What
- A new plugin lifecycle hook event,
session.surfaces(plural), was added alongside the existingsession.surface, running a different handler against the plugin. - A new
$.session.surfacescontrol endpoint was added, returning the list of all attached drawing surfaces (terminal first, if bound); the existingsession.surfaceendpoint now derives its answer from the same shared helper. - The allow-listed set of capability names available to the plugin/hook SDK grew to include
session.surfaces(alongside the existingsession.surface) andconfig.list(alongside existing capabilities liketool.register/command.list).
Why
Previously plugins/hooks could only ask about a single bound surface; session.surfaces lets them see everything a session has attached, which matters for plugins that need to target or coordinate across multiple surfaces.
Names in the bundlesession.surfaces
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What a "surface" refers to beyond a terminal, and what consumes this endpoint, is not stated.