{"version":"2.1.307","anchor":"tool-results-now-record-who-permitted-a-run-permitted-by","canonical_anchor":"tool-results-now-record-who-permitted-a-run-permitted-by","heading":"Tool results now say who allowed the action to run","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/tool-results-now-record-who-permitted-a-run-permitted-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Tool results now say who allowed the action to run\n\nWhen a tool call runs, its result now records who permitted it, or \"unasked\" when no permission was asked for\n\n**What**\n\nA tool call is a single action Claude takes, such as running a command or editing a file. When one runs, the result sent back to Claude now includes a `permitted_by` field next to the existing `ran_on` field. It names whoever approved the call. When nothing asked for permission, it reads \"unasked\". Notes about the session are now added to the result separately.\n\n**Why**\n\nClaude can now see in a tool result whether a person or a rule approved the action, or whether no approval was needed.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}