[52] Inject should prefer direct login to 1Password even if Connect server connection is configured

You are right that the direct connection is less constrained. However, arguments can be made for defaulting to the Connect backend too. Most notably, speed and removing the dependence on the availability of 1Password.

Being signed in and using multiple accounts at once is actually possible: https://developer.1password.com/docs/cli/use-multiple-accounts. Let me know if this piece of our documentation helps.

I am going to take this up with my team, and see what the consensus is here. I will follow up on this thread with future updates :chuffed:

In the meantime, let us know if you have any other feedback/suggestions. We're here to listen and to help. Once again, thank you for trying out our beta.

Best,
Horia

@"Horia.Culea_1P"
A flag would work, but a simple "if signed-in use direct else use Connect" would be even better. That way users don't have another flag to set. The way I see it direct connection should always be preferred because it is less constrained.

Of course, I'm speaking from the perspective of someone whose direct account matches the Connect one. I don't have multiple accounts in op either, but regardless you can only be signed into one account at a time, right?

Hey @nikolamilekic , and thank you for your suggestion!
Indeed, I agree that it would be super nice to have the ability to select the backend that should process your request. I imagine the current behaviour of the CLI can be quite cumbersome, especially when you'd like to use your Connect credentials and the 1Password CLI in the same session. I am going to take this up with my team, during our next meeting.
Would toggling the selected backend via a flag, for example, work in your specific usecase? If not, can you provide us more insight into what exactly is your setup, and what you're trying to achieve?
Once again, thanks for trying our beta CLI! Keep the good suggestions coming, we're here to listen and to help!

Best,
Horia