[URGENT] Trouble logging in at hub.atuin.sh

Help
1

My l/p is in my pw store so I’m quite sure they are correct, but the UI doesn’t accept them. I have two l/p pairs on file for some reason, tried all 4 combinations of them, no luck.

I’ve also tried Google and GH logins, no luck.

Tried Password reset twice, got the email in both cases, entered a new pw, then got an 500 error in both cases.

What to do? This is actually urgent for me because I have some secrets in my Atuin sync history that I want to get wiped ASAP.

2

I can’t help here, but before the cavalry arrives, could you post the output of

  • atuin doctor and
  • atuin status?

Also, are you using sync v2?

[sync]
records = true
3

Thanks for the quick response.

Here is all the info:

atuin doctor
Atuin Doctor
Checking for diagnostics


Please include the output below with any bug reports or issues

{
  "atuin": {
    "version": "18.16.1",
    "commit": "",
    "sync": {
      "auth_state": "Hub (legacy token — run 'atuin login' to upgrade)",
      "records": true,
      "auto_sync": true,
      "last_sync": "2026-06-04 11:48:47.35651 +00:00:00"
    },
    "sqlite_version": "3.46.0"
  },
  "shell": {
    "name": "zsh",
    "default": "zsh",
    "plugins": [
      "atuin"
    ],
    "preexec": "built-in"
  },
  "system": {
    "os": "Darwin",
    "arch": "arm64",
    "version": "26.5.1",
    "disks": [
      {
        "name": "Macintosh HD",
        "filesystem": "apfs"
      },
      {
        "name": "Macintosh HD",
        "filesystem": "apfs"
      }
    ]
  }
}

atuin status
Atuin v18.16.1 - Build rev 

[Local]
Sync frequency: 5m
Last sync: 2026-06-04 13:48:47.35651 +02:00:00
[Remote]
Address: https://api.atuin.sh
Username: vdavid

plus I get this, not sure what the “legacy sync session” part means:

atuin login
You have a legacy sync session. Continuing login to upgrade to full Hub authentication.
IMPORTANT
If you are already logged in on another machine, you must ensure that the key you use here is the same as the key you used there.
You can find your key by running 'atuin key' on the other machine.
Do not share this key with anyone.

Read more here: https://docs.atuin.sh/guide/sync/#login

and then the rest would be the login flow which doesn’t work for me.

4

Hey David!

Sorry it took a second to get to this!

The quick explainer is that we moved all auth to the web hub. If you had an account registered from the CLI, the two need linking.

If you never registered a hub account, and only have a CLI account, you can login to the hub with your CLI credentials and we automatically handle the migration.

If you already have both a hub AND cli account, you can visit the cli-sync part of your user settings on your hub account, and link them from there

I just checked, and it looks like you have both, with the hub account having been created in July last year.

More general advice than Atuin specific, but if any secret is ever entered into your shell history that is super critical, you should consider it compromised and roll the secret.

You system still writes this to your disk in plaintext, so it is likely sat there for any program to read.