You'll notice
Useful3 Signal3
Messages from another agent no longer arrive as one giant summary with the body buried inside.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a message from another agent arrives with its whole body stuck inside the summary field, Claude Code now detects the leaked closing tag and message opener and splits summary and body back out, so the recipient sees a real message rather than a giant summary.
Details
- Two forms are handled and reported separately, one where the leaked markup is namespaced and one where it is bare.
- Repair is refused when the trailing text still looks like leftover markup or JSON, in which case the message is left alone rather than mangled further; those cases are reported as unrepaired markup or unrepaired JSON.
- Summaries are still derived and truncated exactly as before.
Evidence
split_slipped_summary_
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.238
Claude is told to stay in a worktree even when it did not create one
Both mention agent
-
v2.1.238
Messaging an agent that is waking up now queues the message instead of erroring
Both mention agent