Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.274 ·

Transcript messages become expandable and collapsible

Message components in the transcript (task, user-channel, cross-session, inbound) now support expanding and collapsing via shared isExpanded/origin/messageId props

Group of 2 Under the hood Internal Changes
JSON All of v2.1.274
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.274,
Internal ChangesSection of the release

Unclear Whether this already produces user-visible collapsible messages or is only internal groundwork is not shown by the finding.

What Several message-rendering components in the transcript view — task messages, user-channel messages, cross-session messages, and inbound/task-notification messages — now receive isExpanded, messageId, and origin props they didn't take before. New render functions support these props along with verbose and taskDelivery, and an existing inbound-message renderer was refactored to delegate to one of them. A single expanded/collapsed value is now computed once per render and passed through consistently to all of these components.

Why This lets any message in the transcript be expanded or collapsed consistently, regardless of what kind of message it is or where it came from.

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 doubtWhether this already produces user-visible collapsible messages or is only internal groundwork is not shown by the finding.

See this entry in the whole of v2.1.274 →

Feedback