Repository navigation
DX: VSCode Plugin does not prompt users to turn on CLI integration and silently fails instead when trying to link an account with OP Desktop APP #217
Description
Your environment
op-vscode version: Version: v1.0.5
VS Code version: Cursor 0.46.8
CLI version: 2.30.3
OS: MacOS Sequoia 15.3.1
What happened?
When setting up the plugin for the first time, if you do not have the 1Password desktop CLI integration checkbox checked in the desktop application, then trying to link an account will silently fail. This results in a bit of googling or poking around to see what went wrong, since there's no directive on what the issue might be.
What did you expect to happen?
The Plugin should probably propogate (or similar) the helpful text from the CLI application when you op signin so you know what to do. Alternatively, throw an error with a link to docs.
$(op signin)
No accounts configured for use with 1Password CLI.
You can either:
- Turn on the 1Password desktop app integration to sign in with the accounts you've added to the app: https://developer.1password.com/docs/cli/app-integration/ for details.
- Add an account manually with 'op account add' and sign in by entering your password on the command line. See 'op account add --help' for details.
- Authenticate using a 1Password service account by setting the 'OP_SERVICE_ACCOUNT_TOKEN' environment variable to your service account token. Learn more: https://developer.1password.com/docs/service-accounts/
- Use 1Password CLI with a Connect server by setting the 'OP_CONNECT_HOST' and 'OP_CONNECT_TOKEN' environment variables to your Connect host and token, respectively. Learn more: https://developer.1password.com/docs/connect/
Notes & Logs
Reacted by Vadym Mykolaichuk
Activity
giladrom commentedon Mar 26, 2025
Thank you for this! I was repeatedly prompted to "Select an account" only to open 1Password Desktop and nothing happening. The bit about the CLI integration checkbox is entirely undocumented.
mykolaichuk commentedon Jul 8, 2026
is anyone checks on issues here? seems like this extension is not getting updated for some reason