{"version":"2.1.267","anchor":"new-sub-agent-veto-under-prompt-tracking","canonical_anchor":"new-sub-agent-veto-under-prompt-tracking","heading":"New sub-agent 'veto under prompt' tracking","tier":"internal","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-sub-agent-veto-under-prompt-tracking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New sub-agent 'veto under prompt' tracking\n\nSubagent telemetry now tracks when a subagent is 'vetoed' under a specific prompt\n\n**Unclear.** What triggers a veto and how it affects a subagent's behavior isn't specified in the finding.\n\n**What**\n\nClaude Code's subagent tracking now includes a `recordVeto` method and an `isVetoedUnder` check, backed by a new map that records whether a given subagent was vetoed under a particular prompt. This data is cleared along with the rest of a subagent's telemetry when it's cleaned up.\n\n**Why**\n\nThis lets Claude Code keep track of veto decisions tied to specific prompts for subagents, though the finding doesn't specify what triggers a veto or how it affects subagent behavior.\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}