{"version":"2.1.274","anchor":"transcript-message-components-gain-isexpandedoriginme","canonical_anchor":"new-expandablecollapsible-message-rendering-components-for","heading":"Transcript messages become expandable and collapsible","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/transcript-message-components-gain-isexpandedoriginme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Transcript messages become expandable and collapsible\n\nMessage components in the transcript (task, user-channel, cross-session, inbound) now support expanding and collapsing via shared isExpanded\/origin\/messageId props\n\n**Unclear.** Whether this already produces user-visible collapsible messages or is only internal groundwork is not shown by the finding.\n\n**What** Several message-rendering components in the transcript view \u2014 task messages, user-channel messages, cross-session messages, and inbound\/task-notification messages \u2014 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.\n\n**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.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}