Claude Code returned an error result: Not logged in · Please run /login

[Saibaba161]

While using the cli, it returned this error - Claude Code returned an error result: Not logged in · Please run /login

If we select continue on a feature branch, it is failing outright saying - Installer cancelled by user.

[gjtorikian]

Hm, occasionally, Claude asks users to log in, usually when a token expires. That's out of our control, it depends entirely on when you authenticate to Claude and how long it's been.

Are you saying that you ran /login, and the process you were running was cancelled?

[Saibaba161]

So, are you saying that I have to install claude code and this uses my sub?

I thought the other way. Like, PostHog.

[gjtorikian]

It is similar to PostHog's -- we have an LLM gateway, so this does not use your subscription (although there is a config option for that).

I'm just trying to discern how you got in the state. What command(s) did you run, or was this launched from within a Claude session?

[Saibaba161]

I did not even have Claude Code installed. I just went into my project and ran the install command.

[nicknisi]

@Saibaba161 Sorry for the issues. Could you try running workos debug state and paste the contents here? That should help us understand better what the issues is.

Also, running workos debug reset should reset and clear what sounds like some stale auth state and should get you going again. You should be able to run workos auth login or run workos install and get an unclaimed environment.

[Saibaba161]

I am getting - zsh: command not found: workos. This is because, I guess, since the cli is not installed, which is what I was trying to install with the "bunx workos@latest install" command.

[nicknisi]

If that's how you were running it before you can swap workos with bunx workos@latest in all the commands above.

[Saibaba161]

Thanks for that.

I ran "bunx workos@latest debug reset". It asked me for confirmation. Selected "Yes". Ran "bunx workos@latest install" again. Failed at the exact same place.

Then, I tried the "bunx workos@latest auth login". It opened the browser, logged me in, gave me a code to confirm. Then, I tried the install command again. Still, it failed at the exact same place.

I thought this might be a package version issue, and tried it without "@latest". Still the exact replica

[Saibaba161]

I also tried, bunx workos. Failed at the exact same point.

Then I tried installing the workos cli via "bun install -g workos". It installed fine.

After installing this, the "workos auth login" command returned "Already logged in". Then I ran, "workos install", still failed at the exact same point.

[nicknisi]

hmm, I wonder if it's something with bunx vs. npx. Will investigate.

[Saibaba161]

Might be. If it is indeed that, the workos commands should work fine, right?

[nicknisi]

they should, yes!