Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Plugin UI requests in remote sessions now try several attached clients

Copy and prompt read, fill and suggest requests from plugins now pass between attached clients in remote sessions, moving on after 5 seconds of silence

Group of 2 You'll notice Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release

Unclear Only the event's description changed, so it is not clear whether the behaviour it describes is in place yet.

What

Plugins, add-ons that extend Claude Code, can ask the screen you are using to do things such as copy text or read, fill or suggest a prompt. In a remote session, more than one client, meaning a window or device showing the session, can be attached. Before, one client was picked through a single lookup.

  • ui_copy and the prompt read, fill and suggest calls (such as ui_prompt_fill) now go through a list of clients. Depending on how the session is connected, the list is first, each or none.
  • Clients are tried in turn, and ones that stayed silent are skipped.
  • Over a remote connection, prompt.suggest is sent only when the owner's account alone writes to the session. A client that does not answer within 5 seconds hands the request to the next attached client that named it.
  • The part that handles these UI requests for stream-json output is now also created for remote connections when a redaction condition holds.

Why

With several screens attached to one remote session, a plugin's request no longer stalls on a screen that is not answering. Another attached client can pick it up instead.

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 doubtOnly the event's description changed, so it is not clear whether the behaviour it describes is in place yet.

See this entry in the whole of v2.1.290 →

Feedback