{"version":"2.1.301","anchor":"oauth-refresh-lock-takes-extra-options","canonical_anchor":"oauth-refresh-lock-takes-extra-options","heading":"Sign-in refresh lock takes extra settings","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/oauth-refresh-lock-takes-extra-options","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Sign-in refresh lock takes extra settings\n\nThe lock Claude Code uses while renewing your sign-in now adds extra settings based on where its lock file lives\n\n**Unclear.** What the extra lock settings change is not shown.\n\n**What**\n\nWhen Claude Code renews your sign-in, it holds a lock (a marker file) so that two copies of Claude Code do not renew at the same moment. Both the current and the older way of taking that lock now add extra settings worked out from the lock file's location.\n\n**Why**\n\nThis may change how Claude Code deals with a lock left behind by a copy that stopped.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}