Claude Code: Sign In With Your Anthropic Console Account
Claude CodeClaude Code added a keyless sign-in option under /login that lets people authenticate with their Anthropic Console account instead of creating an API key. Anthropic built the option for organizations whose policies don't allow individual API keys, giving them a browser-based OAuth path into Claude Code. The addition sits alongside the existing "create an API key" flow rather than replacing it, and appears in version 2.1.243, released August 24, 2026.
Key Takeaways
- A new keyless option lets Console-billed users sign in to Claude Code through the browser instead of generating an API key.
- Built for locked-down organizations, this option targets companies whose security policies prohibit individual API keys.
- Billing still routes through the Console account, so nothing changes about how usage is tracked or paid for.
- It supplements, not replaces, the existing "create an API key" flow, which remains available for automation and CI use cases.
- The change shipped in Claude Code 2.1.243, released August 24, 2026, alongside a large batch of reliability fixes.
- It follows a broader pattern in Claude Code's recent releases of reducing authentication friction for teams with strict access controls.
A New Way to Sign In
Claude Code's /login command now offers a second path into the tool for people whose organizations use the Anthropic Console for billing and access control. Previously, Console-billed teams typically needed an individual API key to get into Claude Code, which some organizations' security policies simply do not permit. Anthropic's new option, labeled "Sign in with your Console account," lets a person authenticate through a standard browser-based sign-in instead, with no key to generate, store, or rotate.
Why It Matters for Organizations
Many companies restrict who can mint API keys, or forbid long-lived keys entirely for compliance reasons. Until this release, that policy could effectively block Console-billed users from adopting Claude Code unless an admin issued and managed keys on their behalf. The new Console sign-in removes that friction: anyone with valid Console credentials can now get a working Claude Code session without an API key ever entering the picture, while billing and usage still flow through the organization's existing Console account.
How It Fits Alongside Existing Options
Claude Code's /login flow already supported signing in with a Claude.ai account (for Pro, Max, and Team subscribers) and creating an API key for Console-based billing. The new option is presented as the recommended path for Console customers, sitting next to "create an API key" rather than replacing it, so teams that prefer key-based automation, CI pipelines, or programmatic access can still use keys where that makes sense.
This change shipped as part of Claude Code 2.1.243, a release that also touched auto mode reliability, remote MCP reconnection behavior, and several terminal and VS Code fixes.