{"version":"2.1.290","anchor":"auth-status-handles-token-sourceapi-key-conflicts-via-helpe","canonical_anchor":"auth-status-handles-token-sourceapi-key-conflicts-via-helpe","heading":"Auth status marks the unused credential, and a clearer gateway file error","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/auth-status-handles-token-sourceapi-key-conflicts-via-helpe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Auth status marks the unused credential, and a clearer gateway file error\n\nThe auth status display marks the credential not in use, and gateway credential restore explains when the file is refused\n\n**Unclear.** How the auth status output looks beyond the not-in-use marker is not settled.\n\n**What**\n\nWhen both a sign-in token and an API key are present, the auth status display now works out which one is actually being used and marks the other with ` \u00b7 not in use`.\n\nOn setups using a gateway (`CLAUDE_CODE_USE_GATEWAY`), restoring credentials from the hand-off file now gives a clearer error when the file cannot be opened because of permissions. Before, the only message said the file was still locked by another process. The message now adds: \"or this process is refused the file: check its permissions. Try again.\"\n\n**Why**\n\nIf a gateway credential restore fails because of file permissions, the message now points you at the permissions instead of only at another process holding the file.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}