Claude Code login: Unified Auth Hub & Opus 5

If you have been running claude login expecting a single sign-in prompt, the latest Claude Code release will surprise you. In v2.1.219 the command is no longer just “log into Claude” — it has become a unified authentication hub for the external services your agent actually talks to.

Here is the exact session I got on a fresh Ubuntu box:

ubuntu@instance-20260722-1637:~$ claude login
╭─── Claude Code v2.1.219 ─────────────────────────────────────────────────────╮
│             Welcome back Luca!                                                │
│   Sonnet 5 · Claude Team · Open Empower                                       │
│               /home/ubuntu                                                     │
╰──────────────────────────────────────────────────────────────────────────────╯

❯ login

● Could you clarify what you'd like to log into?
 ☐ Login target

What would you like to log into?

❯ 1. GitHub (gh CLI)
     Authenticate the gh CLI for GitHub access
  2. Google Cloud (gcloud)
     Authenticate gcloud for GCP access
  3. npm
     Authenticate npm for package publishing/registry access
  4. Something else
     Specify a different service or tool
  5. Type something.
  6. Chat about this

Enter to select · ↑/↓ to navigate · Esc to cancel

Instead of a one-shot OAuth flow, claude login now asks what you want to authenticate. That is a meaningful shift in how the CLI thinks about identity.

Why a Unified Auth Hub Matters

A coding agent does not live in a vacuum. It pushes to GitHub, deploys to Google Cloud, and publishes packages to npm. Previously you had to remember the right native CLI for each — gh auth login, gcloud auth login, npm login — and keep those credentials fresh alongside Claude’s own session token.

Now a single command centralizes that workflow:

• GitHub (gh CLI) — authenticate the gh CLI so the agent can open PRs, read issues, and run Actions.
• Google Cloud (gcloud) — authenticate gcloud for GCP access, handy when Claude provisions infrastructure or runs gcloud commands in a sandbox.
• npm — authenticate for package publishing or private registry access.
• Something else / Type something — bring your own service or describe what you need.
• Chat about this — stay in the loop and ask Claude to reason about the auth step instead of executing it.

For platform engineers wiring Claude Code into CI/CD, this is one fewer moving part to document and one more place where the agent can self-verify its own credentials before it touches your fleet.

What Else Landed in v2.1.219

The release notes for this build ship three changes worth your attention:

1. Claude Opus 5 is the new default Opus

claude-opus-5 is now the default Opus model — 1M context window, with a fast mode priced at $10 / $50 per million tokens (input / output). Switch anytime with /model. For long-horizon refactoring across large codebases, that context ceiling is the headline feature.

2. sandbox.network.strictAllowlist

A new sandbox.network.strictAllowlist setting lets you deny non-allowlisted hosts for sandboxed commands without prompting. If your security posture requires that sandboxed code never phones home to an unapproved endpoint, this setting enforces it silently instead of interrupting the agent mid-run.

3. DirectoryAdded hook

A new DirectoryAdded hook fires after /add-dir or the SDK register_repo_root control request registers a new working directory. That gives you a clean extension point to run setup, linting, or policy checks the moment a new repo root enters the agent’s scope.

Practical Takeaways

• Run claude login once and treat it as your agent’s identity cockpit, not just a Claude sign-in.
• If you are on Opus, expect the default to be claude-opus-5 — verify with /model before a big billable session.
• Lock down sandboxed network egress with sandbox.network.strictAllowlist for any shared or production environment.
• Hook into DirectoryAdded to automate onboarding checks when new directories are added.

Claude Code keeps moving fast. A command that used to be a single OAuth prompt is now a consolidation point for your whole toolchain — which is exactly what you want from an agent that is about to start pushing code on your behalf.

Read the full notes with /release-notes inside the CLI.