Claude CLI Login 101 · Lesson 1

A success screen is not session state

Separate browser success from the state the CLI actually reads.

By the end

Separate browser success from the state the CLI actually reads.
Apply the safe command for this step.

The big idea

The success page confirms web authorization. It does not prove the credential was written and read by the CLI.

Think of it like… Think of a turnstile flashing green but not writing access to the badge. The light is one step; the badge working later is proof.

The first authorization completed, yet auth status stayed false. That placed the failure after the browser and before local persistence.

In one picture

Before: success stopped before becoming local session state.

Try it

claude auth status
"loggedIn": true

Remember: A screen is a clue; the command is proof.

Quick check

Which proof confirms local state?

Use evidence that crosses the real boundary without exposing a secret.