{"version":"2.1.246","anchor":"transcript-rows-reuse-a-cached-view-of-what-they-depend-on","canonical_anchor":"transcript-rows-reuse-a-cached-view-of-what-they-depend-on","heading":"Transcript rows reuse a cached view of what they depend on","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/transcript-rows-reuse-a-cached-view-of-what-they-depend-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Transcript rows reuse a cached view of what they depend on\n\nTranscript rows cache what they render from, which should reduce redraw cost.\n\n**What**\n\nEach transcript row now caches a narrowed view of the data it renders from, rebuilt only when a generation counter changes and a deep comparison shows something it depends on actually moved. A rendering-cost change with no visible surface.\n\n**Details**\n\n- The cached view covers sibling tool-use ids, progress messages, hook counts, tool results and uses, and the sets of resolved and errored ids.\n\n**Evidence**\n\n`firstTextBlockUuidByMessageID`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}