Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.233 Home All releases olderv2.1.232 v2.1.234newer
Claude Code v2.1.233

Fleet view shares one cut/yank buffer across its inputs

You'll notice
Useful2 Signal2
Background Tasks

In fleet view, text cut in one input can now be pasted into another.

What

Text you cut in one fleet view input can be yanked into another. The fleet view now creates its own kill ring and hands it to every input it renders, instead of each input falling back to the process-wide default.

Details
  • The kill ring (the buffer holding cut text for later yanking) is created once by the fleet view host state and passed down through a provider.
  • Inputs outside the fleet view are unaffected and still use the ambient default.
Evidence

killRing: k7o(),

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.233 →