Our community is getting an upgrade on July 2nd! Learn more in the FAQs →
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.
Feature Request - MCP Limiting Controls
I really love using the MCP service with Claude CLI on my Mac, but it bothers me that it can somewhat easily see all my Vaults. Feature Request Please implement in the 1password App's MCP Settings: 1. Ability to toggle read access for individual vaults 2. Ability to toggle write access for individual vaults Mock-up Here's what I'd like in the 1Password App settings - This would be great for easing my mind specifically not that I don't accidentally give it keys to my kingdom (like the bank) (Props @ GPT and my ability to write a simple prompt) Failed Work-Around Attempt I tried creating another family member account in my family org and just shared the Vaults that I wanted my Claude to use with that, but the desktop app won't let me sign in to multiple accounts in the same org at the same time and I'm not really sure this would have been a good enough work-around for me anyway. The feature I'm requesting above would solve this perfectly. Successful Work-Around Attempt - But sucks So as it stands, the best that I guess I can do is login to my 1password desktop app with only to the dedicated account I made for Agentic access. This would not give any read-only support either, which is not epic.
Face recognition unlock for 1Password
I found the exact topic of my issue as well - not sure why the post was closed without ever posting any response other than some diagnostics... https://1password.community/discussion/138500/howdy-facial-recognition-doesnt-integrate-with-1password-in-fedora-37 I'm also running the latest RPM-based version. I've followed the thread mentioned to add the schema line to my settings file, and I do get a fingerprint button. When tapping it, I just get the password entry. To enable howdy, you need to add the howdy PAM authenetication step to the polkit service's authentication: add the line to /etc/pam.d/polkit-1 : auth sufficient pam_python.so /lib64/security/howdy/pam.py and restart polkit: sudo systemctl restart polkit.service 1Password Version: Not Provided Extension Version: Not Provided OS Version: Fedora 39 Browser: Not Provided
Can we get 1st-party support for keyboard shortcuts?
Now that the interface to edit/set keyboard shortcuts has been removed from 1Password running under Wayland, It would be preferable if the installation package made the shortcuts available to configure by default, rather than https://support.1password.com/keyboard-shortcuts/?linux#wayland. I wrote about this before under a blog of post yours, but it was ignored. It's trivial to add Desktop Action sections to your existing launcher file, and reference them in an Actions= directive: [Desktop Entry] Name=1Password Exec=/opt/1Password/1password %U Terminal=false Type=Application Icon=1password StartupWMClass=1Password Comment=Password manager and secure wallet MimeType=x-scheme-handler/onepassword;x-scheme-handler/onepassword8; Categories=Office; Actions=Show;QuickAccess;Lock;Fill; [Desktop Action Show] Name=Show 1Password Icon=window-symbolic Exec=1password --show [Desktop Action QuickAccess] Name=Show Quick Access Icon=search-symbolic Exec=1password --quick-access [Desktop Action Lock] Name=Lock 1Password Icon=lock-symbolic Exec=1password --show [Desktop Action Fill] Name=Fill in Browser Icon=web-browser-symbolic Exec=1password --fill Putting a symlink to this expanded .desktop file under /usr/share/kglobalaccel/ makes those keyboard shortcuts appear in KDE Plasma's Settings app:
Service Accounts in the GUI?
Are service accounts supposed to be manageable in the GUI/desktop app? I'm running Linux, and I don't see them in my account, despite being on the subscription that has them and them being available on the website. And if not, is this a feature that is coming soon? Because it's fairly impractical to manage them through the website. I'd also add that it's annoying having to recreate the service account every time I want to change permissions on it (add a vault, remove a vault, adjust a vaults permissions, rename it, etc). I understand that you've made it this way for additional security, but I don't think it's actually buying much added security in most circumstances, and I think it should at least be opt-out.
TPM support for Linux
The TPM/Touch ID support 1Password has on Windows and MacOs is a great mix between security and usability and it's the biggest disparity I notice when switching to my Linux machine. There is an old post with a reply saying it was not on the roadmap but since then there were other posts talking about the reboot issue and TPM on Linux so maybe the roadmap changed?
1Password for Linux 8.12.22 Show in Large Type display issue
I just updated to the latest 1Password for Linux 8.12.22 (81222017) Production channel (stable) on Fedora 44 Workstation, GNOME 50. When opening a password with the "Show in Large Type" option, the new window that is created in GNOME desktop is tiny, only shows a single letter rather than previously showing all of the password in a grid. When I click the "Reveal al" text that can be read. the grid then expands vertically down the screen, rather than a rectangle grid box. It's not clear why it has started doing this, or when. I don't use the "Show in Large Type" option very much.Linux beta breaks git signing - removes execute bit on op-ssh-sign
I ran into an error today after updating the Linux client from stable to the latest beta. When I went to commit git chang.s the commit failed with this error: fatal: cannot exec '/opt/1Password/op-ssh-sign': Permission denied error: fatal: failed to write commit object Someone in their great wisdom broke 1Password by removing permissions. The file permissions change from working: .rwxr-xr-x@ 3.9M root root 20 Apr 22:22 onepassword-mcp .rwxr-xr-x@ 1.5M root root 20 Apr 22:22 op-ssh-sign To whatever something thought this is going to do: .rw-r-Sr--@ 3.8M root onepassword-mcp 14 May 04:24 onepassword-mcp .rw-r--r--@ 1.5M root root 14 May 04:24 op-ssh-sign Please fix the file permissions for the git signing functionality.
Linux Nightly Client No Longer Connects With Browser
The current Linux nightly client as of a week or so ago no longer connects with the browser extensions, I have tested on a handful of browsers (Firefox stable/beta/nightly and and chrome stable/dev, all system installed, not flatpak) with both the stable and dev extension and they are longer talking at all, browser extensions act as if no client is installed and want to login with the web. Another machine running the same os (Pop OS) with the stable client continues to work as expected. This started around a week or so ago, just wanted to make sure it was a known issue.
