{"version":"2.1.271","anchor":"plugin-commandrun-now-threads-an-originrootevent-chain","canonical_anchor":"plugin-commandrun-now-threads-an-originrootevent-chain","heading":"Plugin command and hook dispatch now track an origin\/rootEvent chain","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/plugin-commandrun-now-threads-an-originrootevent-chain","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Plugin command and hook dispatch now track an origin\/rootEvent chain\n\nPlugin command runs and hook dispatches now carry origin and rootEvent tracking information\n\n**What**\n\n- The plugin `$.command.run` call changed its signature to accept a destructured `{origin, rootEvent}` object (instead of positional arguments), and now registers the queued command's origin and root event before dispatching it.\n\n- Plugin hook dispatch bookkeeping now also records a `rootEvent` and a new `isPersonInput` flag alongside the existing `turnHeld` field.\n\n**Why** This lets Claude Code trace a command or hook dispatch back to the event that originally triggered it, which is groundwork for more accurate attribution of actions within a session.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}