Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

New session.surfaces plugin/hook endpoint added alongside session.surface

Plugins and hooks gain a session.surfaces (plural) endpoint listing all attached drawing surfaces, plus a matching lifecycle hook event

TierNothing to try yethow much it should matter to you
Useful3my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaPlugin Hookswhat it touches
KindNew Featuresin v2.1.269,
Group of 3 Nothing to try yet Notable 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 existing session.surface, running a different handler against the plugin.
  • A new $.session.surfaces control endpoint was added, returning the list of all attached drawing surfaces (terminal first, if bound); the existing session.surface endpoint 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 existing session.surface) and config.list (alongside existing capabilities like tool.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.

Read from
Names in the bundlesession.surfaces
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 session.surfaces does differently from the existing session.surface event is not specified.

See this entry in the whole of v2.1.269 →