{"version":"2.1.321","anchor":"remote-tool-call-approvals-record-who-decided","canonical_anchor":"remote-tool-call-approvals-record-who-decided","heading":"Remote approvals now keep a record of who made the decision","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-tool-call-approvals-record-who-decided","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote approvals now keep a record of who made the decision\n\nOn remote hosts, a tool-call approval now keeps who decided it, and a reused earlier answer keeps its original decider\n\n**What**\n\nA tool call is a single action Claude takes, such as running a command, and some need your approval first. When Claude Code runs on a remote host, the stored approval for a tool call used to keep only the rule that asked for it. It now also keeps who made the decision.\n\nWhen an earlier answer is reused for a later call, the reused approval carries the original decider rather than losing it.\n\n**Why**\n\nOn remote hosts, an approval can be traced back to whoever actually made it, even when that answer is reused.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}