{"version":"2.1.280","anchor":"sessionmessage-pipeline-now-threads-a-fromplugin-flag","canonical_anchor":"sessionmessage-pipeline-now-threads-a-fromplugin-flag","heading":"Session\/message pipeline now threads a fromPlugin flag","tier":"internal","area":"Messaging","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/sessionmessage-pipeline-now-threads-a-fromplugin-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Session\/message pipeline now threads a fromPlugin flag\n\nInbound session messages can now carry a flag marking whether they came from a plugin\n\n**Unclear.** The finding shows the flag being threaded through but does not say what behavior actually changes based on its value.\n\n**What**\n\nThe internal code that classifies incoming session messages (the same code that already tracks things like grouping IDs, Slack origin, and activity tracking) now also takes in a `fromPlugin` value. This means messages can be tagged with whether they originated from a plugin, a package that extends Claude Code with extra capabilities.\n\n**Why**\n\nTagging messages by their plugin origin lets Claude Code tell plugin-generated content apart from other message sources, which is a building block for handling plugin messages correctly elsewhere in the pipeline.\n\n- Area: Messaging\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}