Claude Code troubleshooting

Claude Code Login Expired: Recover OAuth Access

Key facts

ScopeClaude Code
Last verified
DecisionCheck that you are using the intended account and authentication mode, then sign in again through the supported login flow. If a fresh session immediately reports an expired token, record the version and exact error before changing configuration. Do not paste credentials into support tickets or repeatedly delete unrelated settings.
Official documentation

Official error evidence (quote only; variants differ)

Official account and usage guidance

Fix expired Claude Code login with account checks, a supported OAuth renewal path, official error evidence and a redacted support checklist.

Last verifiedOctober 19, 2026
Quick fix

Check that you are using the intended account and authentication mode, then sign in again through the supported login flow. If a fresh session immediately reports an expired token, record the version and exact error before changing configuration. Do not paste credentials into support tickets or repeatedly delete unrelated settings.

What exact error is documented?

OAuth token has expired.

Documented variant, not every possible message. Official source repository or documentation, checked 2026-10-19.

Match the symptom

  • OAuth token has expired.
  • A completed sign-in or a visible allowance does not match what the current client can do.

First checks

Collect evidence before changing configuration

Inspect installation
claude --version
claude doctor
Re-authenticate inside Claude Code
/login

Diagnosis 1

Which account and authentication mode are active?

Confirm whether this session uses a subscription login, API access or an organization-managed provider. Those modes have different credentials and billing. Compare the account shown in the client with the account you intended to use. A successful browser sign-in alone does not prove that the running terminal refreshed its session.

  1. Read the authentication screen without copying any token.
  2. Check that the browser account matches the intended organization.

Diagnosis 2

Does the supported login flow renew this session?

Use the documented login path in the affected client, then test a small read-only request. If the browser callback cannot return to a remote shell, use the official remote-login guidance. Avoid a loop of reinstalling the application: installation health and expired authentication are different layers with different evidence.

  1. Finish the normal login flow yourself in the browser.
  2. Restart only the affected client and verify the result.

Diagnosis 3

What if the error returns immediately?

Record whether a new login works once, never works, or fails after a network interruption. That distinction helps support investigate refresh state instead of guessing at a password problem. A user report in the official tracker documents the quoted symptom; it does not prove the same root cause on your machine.

  1. Record timestamp, operating system, client version and redacted error.
  2. Use official support with the evidence bundle rather than posting credentials.

If it still fails, send this evidence

A useful support request is reproducible and does not expose credentials.

  • Client version, operating system and work surface.
  • Exact error, timestamp and timezone, with credentials removed.
  • Account/workspace type and the displayed reset time, without private identifiers.
  • Last successful operation and a small reproducible read-only request.

Related paths

All troubleshooting guides

Related account failures

Frequently asked questions

Will reinstalling reset a usage allowance?

No. A service-side allowance belongs to the account. Reinstall only for an installation problem supported by diagnostics, and use the displayed reset or official support for an account restriction.

Should I post my authentication files for support?

No. Share the error, version, time and a redacted account-mode description. Never upload token files, API keys or an unredacted environment dump.

How do I know the fix worked?

Confirm the intended account and run one small read-only request. Check the resulting usage state before resuming the larger task.

Official sources

Commands and product behavior were checked against first-party documentation on October 19, 2026. Interfaces and authentication flows change; recheck the source when applying this across a team.