{"version":"2.1.247","anchor":"subagent-transcripts-can-be-fetched-one-agent-at-a-time-inst","canonical_anchor":"subagent-transcripts-can-be-fetched-one-agent-at-a-time-inst","heading":"Subagent transcripts can be fetched one agent at a time instead of all up front","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/subagent-transcripts-can-be-fetched-one-agent-at-a-time-inst","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Subagent transcripts can be fetched one agent at a time instead of all up front\n\nResuming a cloud session can fetch subagent transcripts one at a time instead of all at once.\n\n**What**\n\nResuming a cloud session previously had to fetch every subagent's events before showing anything. A new path fetches a single agent's transcript when it is actually asked for, at most once per agent, skipping agents whose transcript was written locally. It is switched on by a boolean handed in when the reader is registered; what sets that boolean is decided outside this code, so how often the lazy path runs depends on the caller.\n\n**Details**\n\n- Concurrent requests for the same agent share one in-flight fetch.\n- Each attempt reports an outcome of hit, empty, superseded, unfiltered, read failure, write failure or aborted, with page count, event count and duration.\n- Failures surface as a dedicated transcript-fetch error rather than an empty transcript.\n- Eager fetching still happens when the caller already prefetched the events.\n\n**Evidence**\n\n`ccr_subagent_lazy_fetch`\n\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}