{"version":"2.1.321","anchor":"config-lock-exit-waits-and-question-timeout-permission-handl","canonical_anchor":"config-lock-exit-waits-and-question-timeout-permission-handl","heading":"Permission, sign-in and config-lock handling gain new cases","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/config-lock-exit-waits-and-question-timeout-permission-handl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Permission, sign-in and config-lock handling gain new cases\n\nClaude Code now handles a question timing out as a permission decision taken from config, plus a new sign-in-ended case and config-lock tracking\n\n**Unclear.** It is not clear what makes a question time out, so it is unclear when a timeout leads to an accept decision.\n\n**What**\n\nThree small changes affect how Claude Code handles permissions, sign-in and its config file:\n\n- A question that times out is now treated like a recheck, which gives an accept decision taken from your configuration.\n\n- A sign-in that has ended is now handled the same way as running out of sign-in attempts or having no sign-in.\n\n- The file watcher now tracks whether it holds the lock on the config file and how many times it waited for that lock when exiting.\n\n**Why**\n\nThese add new states to permission, sign-in and config-lock handling.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}