[BUG] CLI Login Issue

Resolved 💬 3 comments Opened May 12, 2026 by Spencer-Schmerling Closed May 15, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Login flow succeeds (welcome banner shows correct account) but no token fields are written to oauthAccount in .claude.json. Every request after login reports "Not logged in." Verified by deleting oauthAccount entirely then re-logging in — the block rebuilds with account identity only, no accessToken/refreshToken/expires fields. Tried full reinstall, daemon restart, fresh shell, file relocation. Running 2.1.139 on Windows.

What Should Happen?

I should be able to use Cluad code.

Error Messages/Logs

Not logged in.

Steps to Reproduce

Login to Claude Code CLI

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

v2.1.139

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗