{"version":"2.1.239","anchor":"relayed-coordinator-messages-are-labelled-and-escaped","canonical_anchor":"relayed-coordinator-messages-are-labelled-and-escaped","heading":"Relayed coordinator messages are labelled and escaped","tier":"notice","area":"Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/relayed-coordinator-messages-are-labelled-and-escaped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Relayed coordinator messages are labelled and escaped\n\nCoordinator messages forwarded to worker agents are labelled and escaped so they can't fake markup.\n\n**What**\n\nWhen a coordinator session forwards a message to a worker agent, the message is now wrapped in a preamble that says whether the text is a copied user message or the coordinator speaking, and the body is escaped so a message cannot fake relay markup.\n\n**Details**\n\n- Only well-formed relay, cited and note tag lines survive unescaped; a line carrying a duplicate attribute is disqualified and escaped.\n- Unicode characters that normalize to angle brackets are escaped too, closing the look-alike route.\n- Recognised attributes on those lines are `id|author|name|session|at|where|thread|edited_at|truncated|attachments`.\n- A `serverEnvelope` option signals that the server handles the wrapping instead.\n\n**Evidence**\n\n`id|author|name|session|at|where|thread|edited_at|truncated|attachments`\n\n- Area: Agents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}