Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
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:
Show the requested credential
I'm heavily using 1password now for agentic usage. All of my business is set up on it now, and all of my credentials are locally using op://, or service accounts. I've put in a lot of effort to try and isolate systems using least privilege, but one problem is that when agents (or applications) request a credential from the system, it doesn't say WHAT credential is being requested. Half the time it doesn't even say the correct name for the application making the request, either. This is a big problem, because I'm starting to get into the habit of just spamming "Accept" blindly. But the whole reason I have set up this whole pipeline is so I can catch malicious programs trying to gain access - for example, supply chain attack infections. Without seeing what credential is being requested, and the process information that is requesting it, I'm finding it's not actually adding much protection at all, because it's putting me into a false sense of security and promoting bad habits. If I'm running multiple agents in parallel, which is often the case, it might just say "Terminal requests access to your vault" or something similar. Which terminal is that? What is the underlying entity being requested? What credential? What is the process ID or terminal title, so I can isolate it to a terminal/agent? Etc. I think this is something that urgently needs to be added. Otherwise, as it stands, it's not really offering much protection because users will just go "oh, it's probably just that agent running - I'm sure it's fine" and accept everything. If that agent happened to have installed a malicious npm package, you'd probably catch it too late.
Linux SSO login issue
When trying to log in on an account behind Google SSO for business account on Linux, after I see the "Redirect Complete You may now close this page, my app just hang's on a spinner. 22:52:32 $ uname -srm Linux 6.14.0-37-generic x86_64 22:52:33 $ 1password --version 8.12.10 INFO 2026-04-20T02:47:03.526+00:00 runtime-worker(ThreadId(48)) [1P:app/op-app/src/app/backend/sso/oidc_verify.rs:87] SSO Authentication -- verifying OIDC redirect. INFO 2026-04-20T02:47:03.526+00:00 runtime-worker(ThreadId(48)) [1P:app/op-app/src/app/backend/sso/oidc_verify.rs:101] SSO Authentication -- sending a notification to B5x to close the identity provider's sign-in tab. INFO 2026-04-20T02:47:03.526+00:00 runtime-worker(ThreadId(48)) [1P:app/op-app/src/app/backend/sso/oidc_verify.rs:191] SSO Authentication -- calling B5's oidc/verify endpoint INFO 2026-04-20T02:47:03.811+00:00 runtime-worker(ThreadId(48)) [1P:app/op-app/src/app/backend/sso/oidc_verify.rs:1106] SSO Authentication -- B5 did not find device credentials for this user/account/device. Beginning enrollment. INFO 2026-04-20T02:47:03.811+00:00 runtime-worker(ThreadId(48)) [1P:app/op-app/src/app/backend/sso/mod.rs:789] Native messaging is not available, cannot use extension first SSO flow INFO 2026-04-20T02:47:03.811+00:00 runtime-worker(ThreadId(48)) [1P:app/op-app/src/app/backend/sso/oidc_verify.rs:795] SSO Authentication -- generating a device key for a new SSO device enrollment. INFO 2026-04-20T02:47:03.811+00:00 runtime-worker(ThreadId(48)) [1P:app/op-app/src/app/backend/sso/oidc_verify.rs:798] SSO Authentication -- attempting to begin device enrollment.
1Password Passkeys not usable in Chromium-based browsers
I’m running into an issue with 1Password Browser Extension and passkeys on Linux and MacOs. Its just not useable anymore. The option “Save and sign in with passkeys” is greyed out. 1Password never appears in passkey login flows. I have the issue on MacOS and Linux with Vivaldi and Chrome. Different machines and different browser but chrome based. With Firefox it works. What I’ve already tried Reinstalling the extension Reconnecting the desktop app Used nigthly builds Installed older chrome versions No change. Can someone help please. Thanks!
Remote Linux machine opens GUI
Setup: Linux Machine that I directly connect to when in the office. Has 1Password installed. Works great. ~/.ssh/config file has ``` Host * IdentityAgent ~/.1password/agent.sock ``` Windows Machine that I directly connect to when in the office or working remotely. Has 1Password installed. Works great. C:/Users/Me/.ssh/config file has ``` Host mypc User me HostName mypc.local ForwareAgent yes ``` The OpenSSH Authentication Agent service has been Disabled and Stopped so that my computer is listening to `\\.\pipe\openssh-ssh-agent` Issue: When sshing into the Linux machine from the Windows machine, git does not work. `git pull` when sshed will open the GUI on my Linux machine (I have watched both screens to test this) I want my WINDOWS machine to open its GUI for me to log in. There's no point to remote in if I can't use the Windows 1Password.User with 1000s of Devices
Hello, I have a question regarding how the 1Password integration with Linux terminals works. We’ve noticed that several employees have over 1,000 devices associated with their accounts in their linked account history, with the vast majority being Linux terminals. Is this expected behavior, or is it something we should be concerned about? Thank you for your insight.Administrators, get a sneak peek at the new sidebar
Starting this month, we’re rolling out a redesigned admin sidebar to create a more consistent and intuitive experience across 1Password products. We’d love your feedback to make sure we’re reaching that goal. Note that this change will only apply to administrators using 1Password for business. What’s changing? Sidebar location: The sidebar has been moved from the right side of the screen to the left side so it's more consistent with the 1Password apps. Improved navigation: Each section of the sidebar now has an icon and we've improved the organization of the pages with tabs. Product switcher: If your team also uses Device Trust or SaaS Manager, you can easily switch to those products from the menu in the top left. What’s the timeline? April 23–May 7: Admins will see an in-product banner inviting you to try the updated sidebar. May 7: The new sidebar becomes the default experience for all accounts. Can we switch back? Yes – if your team prefers to stick with the existing sidebar for now, you can revert to the old design through your settings during the early access period. Here’s how: Select your account name in the top right, then select Manage Account. Toggle “Admin console design updates” off. Please reply below with any thoughts, ideas, or questions! Your feedback is invaluable in helping us continue to improve 1Password.
