{"version":"2.1.314","anchor":"new-error-when-a-managed-api-key-helper-blocks-the-stored-cl","canonical_anchor":"new-error-when-a-managed-api-key-helper-blocks-the-stored-cl","heading":"Clear error when an administrator's API key helper stops your claude.ai login being sent","tier":"notice","area":"Auth","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/new-error-when-a-managed-api-key-helper-blocks-the-stored-cl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Clear error when an administrator's API key helper stops your claude.ai login being sent\n\nClaude Code now explains when it held back your claude.ai login because your administrator's API key helper is not in effect\n\n**Unclear.** What causes the API key helper to be out of effect, and so when this error appears, is not stated.\n\n**What**\n\nAn API key helper is a script an administrator can set up to supply the key Claude Code uses to sign in. Claude Code has a new error for one case: it did not send your claude.ai login because the API key helper your administrator set is not in effect. The message tells you to run `\/status` to see where each of your settings comes from.\n\n**Why**\n\nIf your organization manages your settings, you now get a plain explanation and a next step instead of an unexplained sign-in failure.\n\n- Area: Auth\n- Names: `\/status`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}