{"version":"2.1.236","anchor":"teammate-messages-whose-summary-swallowed-the-body-are-split","canonical_anchor":"teammate-messages-whose-summary-swallowed-the-body-are-split","heading":"Teammate messages whose summary swallowed the body are split back apart","tier":"notice","area":"Agent Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/teammate-messages-whose-summary-swallowed-the-body-are-split","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Teammate messages whose summary swallowed the body are split back apart\n\nMessages from another agent no longer arrive as one giant summary with the body buried inside.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Two forms are handled and reported separately, one where the leaked markup is namespaced and one where it is bare.\n- 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.\n- Summaries are still derived and truncated exactly as before.\n\n**Evidence**\n\n`split_slipped_summary_`\n\n- Area: Agent Messaging\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}