{"version":"2.1.281","anchor":"credential-filekeychain-change-now-triggers-an-extra-refres","canonical_anchor":"credential-filekeychain-change-now-triggers-an-extra-refres","heading":"Credential file\/keychain change now triggers an extra refresh step","tier":"internal","area":"Auth","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/credential-filekeychain-change-now-triggers-an-extra-refres","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Credential file\/keychain change now triggers an extra refresh step\n\nWhen your stored login changes in the keychain or .credentials.json, Claude Code now runs an extra refresh step\n\n**Unclear.** The finding does not say what the extra refresh step does.\n\n**What**\n\nClaude Code watches where your login is stored: the system keychain and the file `.credentials.json`. When either one changes, it now runs an additional refresh step after clearing its cached copy. Before, it ran only one step.\n\nIt also now keeps track, in `keychainHoldsItem`, of whether the keychain currently holds the login item.\n\n**Why**\n\nMore work now happens when your stored login changes, for example after signing in again elsewhere.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}