REMINDER: the community will be in read-only mode from tomorrow until July 2nd. This is part of our platform upgrade! Learn more in the FAQs

Forum Discussion

tom_isaacson's avatar
tom_isaacson
New Contributor
10 days ago

No environment support in Linux

I tried following the instructions at https://www.1password.dev/cli/secrets-environment-variables. It says "use version 2.33.0-beta.02 or later" and I have 2.34.1 on Ubuntu but I get:

$ op run --environment
[ERROR] 2026/06/12 08:32:31 unknown flag: --environment

I tried upgrading to 2.36.0-beta.03 but that fails to login:

$ ./op_v2.36.0-beta-03 vault list
[ERROR] 2026/06/15 09:14:33 connecting to desktop app: read: connection reset, make sure 1Password CLI is installed correctly, then open the 1Password app, select 1Password > Settings > Developer and make sure the 'Integrate with 1Password CLI' setting is turned on. If you're still having trouble connecting, visit https://www.1password.dev/cli/app-integration#troubleshooting for more help.

 

2 Replies

  • I was just searching this up and ran into your reply 1h after you posted. How fortunate! Thank you for taking the time to share this.

  • Reponse from 1Password:

    The --environment flag for op run is currently only available in beta builds of 1Password CLI, not in stable releases.
    Version 2.34.1 does not include this flag. To use this feature, you need to install the latest beta build from: https://app-updates.agilebits.com/product_history/CLI2#beta

    Before installing the beta version, ensure you remove the stable 1password-cli package, as keeping both can cause version conflicts. Also when switching to beta CLI build, and existing authentication is not carried over, you will need to re-authenticate on the beta build using one of the following methods:

    • Desktop app integration: Ensure Integrate with 1Password CLI is enabled in the 1Password app under *Settings > Developer*, then the CLI will authenticate automatically.
    • Service account: Re-export the service account token: export OP_SERVICE_ACCOUNT_TOKEN=<token>
    • Manual sign-in: Run op signin in the terminal.

    I copied the beta op to /usr/bin/op then ran op signin and that fixed it.