Thanks for the report. We're tracking this issue but don't have an ETA for a resolution yet.

We're aware of an issue with CLI sessions not persisting for certain actions after a recent authentication update. A fix is being worked on. Can you confirm which version of the CLI you are using ( railway --version) -- 4.39.0 is the latest?

What happened when you tried to create a token? Did you set the RAILWAY_API_TOKEN environment variable in your shell profile (e.g., .bashrc or .zshrc) so it persists across sessions without requiring railway login?

I'm using railway 4.38.0 version.

I tried the RAILWAY_API_TOKEN approach, but LLM complained that there were not enough access to list projects and the token AUTH is no good for that.

You would want to be using a token that is not scoped to any single workspace.

It still keeps happening.

```

railway --version

railway 4.43.0

```

Doing the auth with railway login

Situation getting even worse

This probably was the fix

Just to clarify, are you still actively running into this issue?

Yes, i do. Still authenticating multiple times per day across at least 2 machines on mac OS.

For some reason i did not receive notification about the question

Thanks for sticking with us on this and for the screenshots.

Tracked this down to a server-side OAuth bug — your CLI's refresh token points at a grant the server can't resolve, so it falls back to prompting login. Not specific to your setup.

The fix for this has been drafted and is in review and should ship soon. Sorry for the annoyance in the meantime!

If you want a workaround, RAILWAY_API_TOKEN works — just make sure the token isn't scoped to a single workspace (Account Settings → Tokens, leave workspace unselected). That was the listing issue you hit earlier.