Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
Shift+Command+X command still shows 1Password in Safari even when changed to another one
Hi! I'm using 1Password Beta 8.5.0 version and 1Password for Safari extension with it, works great. But I noticed a problem - when editing text in Google Docs, I often use Shift+Command+X combination as it makes text cross-through (very convenient to quickly mark things as done in a document). I redefined the keyboard shortcuts in 1Password, but when I use the combination, it still shows 1Password in Safari. Can this be fixed? Thank you!
1Password Version: 8.5.0
Extension Version: 2.1.4
OS Version: macOS 12.1
I'm happy to share that Safari 26, included with macOS Tahoe, now includes the ability to change browser extension keyboard shortcuts. 🎉
This means you can change the default shortcut (Command–Shift–X) for opening the 1Password pop-up, in case you already use that combo for something else. Here’s how to set it up:
- Update to macOS Tahoe.
- Open Safari.
- Click on Safari next to the  Apple logo in the menu bar and then click Settings.
- Click Extensions.
- Choose 1Password then scroll down and edit the shortcut.
I hope that helps!-Dave
4 Replies
- 1P_Dave
Moderator
I'm happy to share that Safari 26, included with macOS Tahoe, now includes the ability to change browser extension keyboard shortcuts. 🎉
This means you can change the default shortcut (Command–Shift–X) for opening the 1Password pop-up, in case you already use that combo for something else. Here’s how to set it up:
- Update to macOS Tahoe.
- Open Safari.
- Click on Safari next to the  Apple logo in the menu bar and then click Settings.
- Click Extensions.
- Choose 1Password then scroll down and edit the shortcut.
I hope that helps!-Dave
Jack_P_1P1Password Team
On behalf of Kevin, you're very welcome @ezaritov! :smile:
kevin_liHi @ezaritov.
Currently, there is no way to change 1Password's shortcuts in Safari, but it is an issue our developers are aware of and are working to improve and implement that feature. I made sure to add your voice to it.
I apologize for the inconvenience it caused.
ref: dev/core/core#9365
