{"version":"2.1.247","anchor":"transcript-view-reads-its-data-from-the-turn-rather-than-fro","canonical_anchor":"transcript-view-reads-its-data-from-the-turn-rather-than-fro","heading":"Transcript view reads its data from the turn rather than from props","tier":"internal","area":"UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/transcript-view-reads-its-data-from-the-turn-rather-than-fro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Transcript view reads its data from the turn rather than from props\n\nThe transcript view was re-plumbed to read from the live turn; nothing should look different.\n\n**What**\n\nThe transcript screen and message list were re-plumbed to take a descriptor of which live turn to render plus a history mode, instead of separate props for messages, in-progress tool ids, conversation id and render caps. Behaviour should be unchanged.\n\n**Details**\n\n- History mode is uncapped in dump mode and \"all\" when showing everything.\n- Rate-limit callbacks are now read off the turn instead of passed in.\n- The streaming preview is read from a store rather than handed over as a prebuilt element.\n- Virtual scrolling is still switched off by `CLAUDE_CODE_DISABLE_VIRTUAL_SCROLL`.\n\n**Evidence**\n\n`trackStickyPrompt`\n\n- Area: UI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}