{"version":"2.1.269","anchor":"new-dispatch-context-helper-and-self-hop-chain-bound-for-cro","canonical_anchor":"new-dispatch-context-helper-and-self-hop-chain-bound-for-cro","heading":"New dispatch context helper and self-hop chain bound for cross-agent posts","tier":"notice","area":"Team Messaging","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-dispatch-context-helper-and-self-hop-chain-bound-for-cro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New dispatch context helper and self-hop chain bound for cross-agent posts\n\nAgent-to-agent message chains now stop themselves after a set number of self-hops or total posts\n\n**What**\n\nA new internal tracker counts how many messages each agent sends to a given recipient, and how many messages have been sent in total since your last turn. When either count crosses a limit (`maxSelfHops` for a single recipient, or `maxChainLength` overall), further posts in that chain are blocked.\n\n**Why**\n\nThis extends the earlier fix that stopped message-forwarding to Claude Desktop from looping forever, applying the same kind of chain-length limit more generally to agent-to-agent messages. It prevents agents from getting stuck sending messages back and forth indefinitely.\n\n- Area: Team Messaging\n- Names: `maxSelfHops`, `maxChainLength`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}