Your account is active and on the Hobby plan, so the issue is on the CLI side where the auth token is not being persisted after browser confirmation. The CLI stores credentials in ~/.railway, so try removing that directory with rm -rf ~/.railway and then running railway login --browserless again. If that still fails, try reinstalling the CLI via the shell script (bash <(curl -fsSL cli.new)) instead of Homebrew, as the Homebrew distribution can occasionally have issues with token storage on newer macOS versions. You can also work around this by generating an account token at https://railway.com/account/tokens and setting it as export RAILWAY_API_TOKEN= in your shell.

$ rm -rf ~/.railway
$ brew uninstall railway
$ bash <(curl -fsSL cli.new)  # as in https://docs.railway.com/cli#shell-script-macos-linux-windows-via-wsl
$ rm -rf ~/.railway  # just in case
$ ls -alt ~/ | grep railway  # no output
$ railway login --browserless
Your authentication code is: XXXX-XXXX
Please visit:
  https://railway.com/activate
Unauthorized. Please run `railway login` again.

Also worth noting, then installing via cli.new installs the same version as with homebrew

This is a known bug with the CLI authentication flow that our team is actively investigating. First, please update to the latest CLI version (4.37.2) - you're currently on 4.36.1 - and try logging in again. If that still fails, you can work around it by generating an API token at https://railway.com/account/tokens and setting it in your shell with export RAILWAY_API_TOKEN=.

❯ railway -V

railway 4.37.2

❯ railway login

> Open the browser? Yes

Unauthorized. Please run railway login again.

I've run into the same problem.

This worked for me

Have you tried rm -rf ~/.railway before running railway login?

This should be fixed in v4.37.4. You can upgrade with:

```

curl -fsSL https://raw.githubusercontent.com/railwayapp/cli/master/install.sh | sh

```

If you installed via Homebrew, uninstall that version first so the new binary takes precedence:

```

brew uninstall railway

```

Let us know if this does not solve your problem.