{"version":"2.1.248","anchor":"clearer-error-when-another-claude-code-process-is-refreshing","canonical_anchor":"clearer-error-when-another-claude-code-process-is-refreshing","heading":"Clearer error when another Claude Code process is refreshing the same login token","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/clearer-error-when-another-claude-code-process-is-refreshing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Clearer error when another Claude Code process is refreshing the same login token\n\nTwo Claude Code processes refreshing your login at once now give a clear wait-and-retry message.\n\n**What**\n\nWhen two Claude Code processes try to refresh OAuth credentials at the same time, the one that loses the race now gets a message naming the cause and pointing at a recovery, rather than a generic authentication failure. The condition is treated as transient rather than a sign that your login is broken, so the suggested response is to wait and try again. Nothing needs enabling.\n\n**Details**\n\n- Fires when another process already holds the credential refresh lock, or when a process exited part way through a refresh and left the lock behind.\n- The plain failure reads `Could not refresh your login because another Claude Code process is refreshing it`.\n- In debug mode the fuller text explains the cause, suggests retrying in a minute, and if it persists suggests closing other Claude Code processes or signing in again.\n\n**Evidence**\n\n`Failed to refresh OAuth token: another Claude Code process is refreshing it or exited mid-refresh. This is usually transient; retry in a minute, and if it persists close other Claude Code processes or sign in again`, `Could not refresh your login because another Claude Code process is refreshing it`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}