{"version":"2.1.301","anchor":"tool-decision-telemetry-gains-permission-mode-and-config-dec","canonical_anchor":"tool-decision-telemetry-gains-permission-mode-and-config-dec","heading":"Tool permission telemetry now records which permission mode was active","tier":"notice","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/tool-decision-telemetry-gains-permission-mode-and-config-dec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Tool permission telemetry now records which permission mode was active\n\nTelemetry on tool permission decisions now includes the permission mode, plus extra detail when a setting made the decision\n\n**What**\n\nEach time Claude Code allows or blocks a tool call (an action Claude takes, such as running a command or editing a file), it can report the decision as a `tool_decision` telemetry event. Telemetry is usage data you can send to your own monitoring through OpenTelemetry, a standard way of collecting it. These events now include:\n\n- `permission_mode`: the permission mode the decision was made under\n\n- Extra fields giving the reason, when the decision came from your configuration\n\nBefore, the event carried only the decision, its source, the tool's name and ID, MCP details and the tool's parameters.\n\n**Why**\n\nIf you collect Claude Code telemetry, you can now see which permission mode was active when a tool was allowed or blocked. This only matters if telemetry is turned on.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}