{"version":"2.1.280","anchor":"agent-to-agent-messages-can-now-carry-a-from-plugin-identifi","canonical_anchor":"agent-to-agent-messages-can-now-carry-a-from-plugin-identifi","heading":"Agent-to-agent messages can now carry a from-plugin identifier","tier":"internal","area":"Messaging","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/agent-to-agent-messages-can-now-carry-a-from-plugin-identifi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Agent-to-agent messages can now carry a from-plugin identifier\n\nAgent-to-agent messages can now carry a from-plugin identifier\n\n**What**\n\nMessages passed between agents or sessions already carried tags like `from`, `from-session`, `hop-chain`, `from-name`, and `from-mode`. They now support an additional optional `from-plugin=\"...\"` attribute, which Claude Code parses into a `fromPlugin` field.\n\n**Why**\n\nThis lets a receiving agent know which plugin originated a message, which matters when multiple plugins are sending messages into the same conversation.\n\n- Area: Messaging\n- Names: `from-plugin`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}