{"version":"2.1.247","anchor":"locally-written-subagent-transcripts-are-marked-so-they-are-","canonical_anchor":"locally-written-subagent-transcripts-are-marked-so-they-are-","heading":"Locally written subagent transcripts are marked so they are not refetched","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/locally-written-subagent-transcripts-are-marked-so-they-are-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Locally written subagent transcripts are marked so they are not refetched\n\nSubagent transcripts written locally are marked so resume does not fetch them again remotely.\n\n**What**\n\nWhen transcript entries carrying a subagent id are written locally, that id is recorded in a do-not-fetch set, so the newer resume path does not pull the same subagent's transcript back from the remote store on demand.\n\n**Details**\n\n- The recording happens before the check that can skip persisting the entry.\n- The surrounding on-demand subagent transcript loading is itself new in this build and only runs when the resume path registers its event reader; without that, none of this is active.\n\n**Evidence**\n\n`noteAgentWrittenLocally`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}