Resuming a teammate with an unreadable transcript now errors instead of silently forgetting everything.
What's wrong with this entry?
Resuming an in-process teammate whose transcript fails to load now raises a visible error instead of quietly continuing with no history, so you are not left talking to a session that has forgotten everything.
- The load now honours cancellation and rethrows it rather than treating it as a failure.
- Any other failure is reported as a transcript load failure and surfaced as an error.
Cannot resume teammate: its transcript could not be loaded
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Another forged control tag is escaped in subagent output
Both mention subagent
-
v2.1.234
Spawned processes get
--flag=valuewhen the value looks like a flagBoth mention subagent
-
v2.1.235
New error for delegating to a subagent without naming one
Both mention subagent