{"version":"2.1.312","anchor":"tengu-tool-use-can-use-tool-rejectedallowed-telemetry-adds","canonical_anchor":"tengu-tool-use-can-use-tool-rejectedallowed-telemetry-adds","heading":"Permission usage data now identifies the individual tool call","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/tengu-tool-use-can-use-tool-rejectedallowed-telemetry-adds","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Permission usage data now identifies the individual tool call\n\nThe usage data Claude Code sends when a tool call is allowed or rejected now includes a scrambled ID for that specific tool call\n\n**What**\n\nA tool call is a single action Claude takes, such as running a command or editing a file. When Claude Code checks whether one is permitted, it sends usage data saying whether the call was allowed or rejected. That data now includes a hashed (scrambled) ID for the specific tool call. Before, it carried only an ID for the message the call belonged to.\n\n**Why**\n\nThis only affects usage data. Nothing changes in how permission checks behave or what you see on screen.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}