Had a look with one of my colleagues over the problem, and currently we're investigating the issue.
The number one lead, at the moment, is related to the lack of USER UUID in the output of op account list. Since the suffix of the environment variable uses the UUID to identify the corresponding session, our hunch is, currently, that the CLI cannot tie the session to a specific user. We're looking into finding out what might have caused the USER UUID to not have been populated during the account add process. Will keep everyone up to date as we find out new details, thanks you everyone for reporting, in the meantime!

Hey folks!

I can reproduce the problem if I start fresh with the CLI and run any command other than op signin or op account add and then add the account when prompted for it. For example:

```
$ op vault ls
No accounts configured for use with 1Password CLI.

You can either:
- Sign in with biometric unlock; see https://developer.1password.com/docs/cli/get-started/#sign-in for details.
- Add an account manually with op account add; see op account add --help for details.

Do you want to add an account manually now? [Y/n] y

And now enter your account details

```

The above steps can cause this exact issue. We are working on a fix for that.

In the meantime, there is also a workaround:
1. Delete the CLI's configuration by running rm ~/.op/config or rm ~/.config/op/config. Warning: this will remove the account's details; make sure you have them stored somewhere else s well.
2. Now run eval $(op signin). You should be prompted for your account details. After entering those, you should be signed in.

Running the above should only be needed once.

Let me know if that helps.

Joris

Can confirm the above fix works, thanks! Also confirm that I first signed in by running op vault ls as per the documentation, so agree that seems to be the cause.

Joris_1P's workaround works for me as well. Thanks, Joris!

I am glad to hear that works! Thank you for confirming that.

I had this same issue and found this thread, I can also confirm the workaround from Joris_1P worked for me.

Thanks!

This issue has been addressed with 2.0.1. Please, do let us know if this is encountered again.
Thank you everyone for reporting!

Best,
Horia