Under the hood
Useful2 Signal2
Subagent transcripts written locally are marked so resume does not fetch them again remotely.
What's wrong with this entry?
Anonymous. No account, no email.
What
When 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.
Details
- The recording happens before the check that can skip persisting the entry.
- 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.
Evidence
noteAgentWrittenLocally
Strings lifted out of the shipped bundle, so the claim above can be checked against them.