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.235 Home All releases olderv2.1.234 v2.1.236newer
Claude Code v2.1.235

Command queue became an instance, and queued commands can be passive

Under the hood
Useful2 Signal2
Elsewhere

Queued commands can be marked passive, and Esc now lets other handlers run when it didn't cancel anything.

Feature flag
tengu_hover_rest Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.235: on

Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you

What

The queue of pending commands is now an object consumers subscribe to rather than a set of process-wide variables. Queued commands gained a "passive" marker, and the Esc/cancel handler now reports whether it actually consumed the key so other handlers can run when it did not.

Details
  • Consumers read state through a snapshot accessor and a subscribe call, and trigger a re-check through a method rather than a free function.
  • Separate predicates select passive and non-passive queued commands, and drains can request only the passive ones.
  • The variant of the queue backed by version 5 storage is created only when the pinned flag tengu_hover_rest is on.
Evidence

getCommandQueueSnapshot

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

See this entry in the whole of v2.1.235 →