{"version":"2.1.293","anchor":"tool-permission-decisions-are-now-recorded-on-the-tool-resul","canonical_anchor":"tool-permission-decisions-are-now-recorded-on-the-tool-resul","heading":"Tool results now record why a tool call was allowed or denied","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/tool-permission-decisions-are-now-recorded-on-the-tool-resul","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Tool results now record why a tool call was allowed or denied\n\nEach tool result now carries a record of the permission decision behind it: the decision, where it came from, and sometimes a reason type\n\n**What**\n\nWhen Claude uses a tool (runs a command, edits a file, and so on), Claude Code keeps a record of the result. That record now also includes the permission decision for the call, meaning whether you or a setting allowed or denied it. The decision record holds:\n\n- the decision itself\n\n- its source, such as the permission dialog you answered\n\n- a reason type, when there is one\n\nBefore, the record only noted things like why a tool did not run, any feedback you typed, and a suggested remedy.\n\n**Why**\n\nThe record of each tool call now says why it was allowed or denied, not just what happened. That makes it easier to see after the fact how a permission was granted or refused.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}