{"version":"2.1.317","anchor":"sign-in-and-sign-out-check-that-config-was-saved","canonical_anchor":"sign-in-and-sign-out-check-that-config-was-saved","heading":"Sign-in and sign-out now check that your settings file was actually saved","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sign-in-and-sign-out-check-that-config-was-saved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Sign-in and sign-out now check that your settings file was actually saved\n\nSign-in now warns if it could not remove the old account or API key from the config file, and sign-out only reports success once that file is saved\n\n**What**\n\nClaude Code keeps your account details in a config file, which is a settings file on your computer. That file can hold an API key, a secret code that lets Claude Code use your account.\n\n- Signing in: Claude Code tries to remove the previous API key from the config file. If that fails, it now says 'A sign-in could not take the last account or API key off the config file.'\n\n- Signing out and restoring a previous account: Claude Code now reports the account as revoked or restored only if the config file was actually saved. Before, it always reported success.\n\n**Why**\n\nAn old API key could be left on disk after you signed in, with nothing telling you. You now get a message when that happens, and a report that you are signed out means the file was really updated.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}