{"version":"2.1.229","anchor":"startup-repair-for-subagent-transcripts-left-as-symlinks","canonical_anchor":"startup-repair-for-subagent-transcripts-left-as-symlinks","heading":"Startup repair for subagent transcripts left as symlinks","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/startup-repair-for-subagent-transcripts-left-as-symlinks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Startup repair for subagent transcripts left as symlinks\n\nOn startup, subagent transcripts stored as symlinks are converted to hard links or copies.\n\n**What**\n\nA startup sweep converts symlinked subagent transcript and metadata files into hard links, or copies them if that fails. It only runs when the newer session storage backend is present, and does nothing at all if the session directory sits outside the transcript store.\n\n**Details**\n\n- Before relinking, it checks the target is inside the transcript store, is not this session's own file, sits beside its transcript, and actually names the agent within the first 64 KiB.\n- Caps how much it does per pass and starts at a random offset, so repeated runs cover different files.\n- Reports counts through `tengu_adopt_relink`; copy fallbacks also increment `task_local_agent\/adopt_link_fallback_copy`.\n\n**Evidence**\n\n`no record naming this agent in the first 64 KiB`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}