{"version":"2.1.271","anchor":"turnstep-plugin-hook-events-now-carry-an-agentid","canonical_anchor":"turnstep-plugin-hook-events-now-carry-an-agentid","heading":"turn.step plugin hook events now carry an agentId","tier":"internal","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/turnstep-plugin-hook-events-now-carry-an-agentid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### turn.step plugin hook events now carry an agentId\n\nThe turn.step hook event now includes an agentId field\n\n**What**\n\nPlugin hooks that intercept or verify a model's turn can listen for a `turn.step` event. That event's data now allows and preserves an `agentId` field, alongside the existing `turnId`, `index`, and `messageCount` fields, and the validation logic that checks incoming arguments no longer rejects that key.\n\n**Why**\n\nThis lets hook code identify which agent a given turn step belongs to, useful in setups involving subagents (separate agent instances handling parts of a task).\n\n- Area: Plugin Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}