{"version":"2.1.242","anchor":"transcript-components-take-one-turn-object","canonical_anchor":"transcript-components-take-one-turn-object","heading":"Transcript components take one turn object","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/transcript-components-take-one-turn-object","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Transcript components take one turn object\n\nTranscript components now share one turn object, and remote sessions write into the same transcript store.\n\n**What**\n\nTranscript components that each received separate streaming, loading and auto-queue callbacks now take a single turn object, with a shared helper deciding whether a response is still streaming. Remote sessions push into the same transcript store rather than setting messages and loading state directly.\n\n**Details**\n\n- The helper prefers an optional `getIsResponseStreaming()` callback and falls back to the turn's mid-turn flag when it is absent.\n- Remote-session hooks now call `setExternalLoading` and `markRemoteTurnComplete` instead of the old message and loading setters.\n\n**Evidence**\n\n`getIsResponseStreaming`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}