{"version":"2.1.282","anchor":"parked-permissions-tool-call-now-runs-only-after-its-stored","canonical_anchor":"parked-permissions-tool-call-now-runs-only-after-its-stored","heading":"An approved tool call waits until its saved permission record is cleared","tier":"internal","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/parked-permissions-tool-call-now-runs-only-after-its-stored","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### An approved tool call waits until its saved permission record is cleared\n\nA tool call left waiting on a permission now runs only once Claude Code confirms its saved record was deleted; otherwise it is held back\n\n**Unclear.** The check is skipped in some situations, and it is not clear how often that happens.\n\n**What**\n\nSometimes a tool call (an action Claude takes, such as running a command or editing a file) is put on hold while it waits for your permission, and Claude Code saves a record of that waiting call. When the call is later let through, Claude Code now first marks the session as running, saves the session's state and deletes that record, with a time limit on the wait.\n\nIf Claude Code cannot confirm the record was deleted, the call does not run. The session goes back to waiting for your action, or to idle, and a warning is written to the log saying the call was not run because its record's delete was not confirmed.\n\n**Why**\n\nThis stops a call you approved once from running a second time when a session is resumed and finds the old record still there.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}