{"version":"2.1.273","anchor":"parked-permission-timeout-no-longer-a-hardcoded-constant","canonical_anchor":"parked-permission-timeout-no-longer-a-hardcoded-constant","heading":"Parked-permission timeout no longer a hardcoded constant","tier":"use","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/parked-permission-timeout-no-longer-a-hardcoded-constant","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Parked-permission timeout no longer a hardcoded constant\n\nThe wait time before a parked permission prompt times out is now configurable, not fixed\n\n**What**\n\nWhen Claude Code \"parks\" a permission request (waiting for you to answer whether a tool can run) and no answer comes back in time, it falls back after a wait period. That wait period used to be a fixed number; it's now read per-request from a setting, which in turn comes from the environment variable `CLAUDE_CODE_PARKED_PERMISSION_WAIT_MS` (still defaulting to 2000 milliseconds).\n\n**Why**\n\nMaking the timeout configurable per situation rather than one fixed value allows more flexibility in how long Claude Code waits for a permission answer before giving up.\n\n- Area: Permissions\n- Names: `CLAUDE_CODE_PARKED_PERMISSION_WAIT_MS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}