Messaging an agent that is waking up now queues the message instead of failing.
What's wrong with this entry?
Sending a message to an agent that is mid-resume used to fail. Both the tool path and the interactive resume path now catch that case and queue the message for the agent's next tool round.
- The queued message is delivered as a meta user message on the agent's next tool round.
- The sender is told the message may not be delivered if the agent turns out to have been stopped.
- Only a task record that is genuinely gone still produces a failure notice.
is already waking; message queued for its next tool round (not delivered if the agent turns out to have been stopped).
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.235
Question options with identical text are no longer confused with each other
Both mention agent
-
v2.1.236
Teammate messages whose summary swallowed the body are split back apart
Both mention agent
-
v2.1.239
Agent messaging can address teammates; routine notification framing added
Both mention agent