Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

New ui.copy plugin API for writing to the clipboard

Plugins can now copy text to the terminal clipboard through a new ui.copy action

Group of 3 Use it now New Features
JSON All of v2.1.280
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
New FeaturesKind: in v2.1.280,
What probably matters to youSection of the release

Unclear What ui.copy actually lets a plugin or hook do is not stated beyond its name.

What

  • A new $.ui.copy plugin-facing function copies text to the clipboard using OSC 52 (a terminal escape sequence for clipboard access), restricted to the terminal surface. It declines with a reason (no-surface or no-clipboard) when there's no attached UI or the text is too long for an OSC 52 write.
  • A matching ui.copy control-protocol action was added to the client, sending the text and an optional surface identifier over the same channel used for actions like ui.focus.
  • ui.copy was added to the capability list used by the plugin/hooks worker sandbox, alongside existing capabilities like ui.open, ui.close, ui.panes, ui.blit, fs.read, and fs.write.

Why This gives plugins and hooks a sanctioned way to put text on the user's clipboard, gated by the same capability and sandbox system as other UI actions, instead of needing a workaround.

Read from
Names in the bundleui.copy
What the documentation says
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 `ui.copy` actually lets a plugin or hook do is not stated beyond its name.

See this entry in the whole of v2.1.280 →

Feedback