Background forks are told that ending the conversation from a fork does nothing.
What's wrong with this entry?
The tool description now has a "Background forks" section saying that forked tasks such as memory consolidation, summaries and suggestions inherit the tool but calling it there has no effect on either the main conversation or the fork, and that a fork with welfare concerns should stop and say so in its output.
In a forked task the tool does nothing: calling it ends neither the main conversation nor the fork.
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