1Password on Omarchy

1Password on Omarchy: the polished commercial password manager

The polished commercial password manager — encrypted vault, autofill, passkeys, and SSH/Git integration that feels native on Linux.

TL;DR install

omarchy pkg add 1password

That’s the full install — the store package pulls the official stable build from the AUR (maintained by 1Password themselves). It takes ~2 minutes. Honest caveat up front: 1Password is paid software. There is no free tier — you get a 14-day free trial, then you need a membership (Individual starts at $2.99/mo billed annually). If you want the free route, skip to Bitwarden below.

Getting started in 5 minutes

1. First launch

Open 1Password from the launcher (or run 1password in a terminal). On first run it walks you through sign-in — no local setup, no wizard mazes. If the window renders oddly under Hyprland, note it for the checklist above; the Electron frontend can be picky on Wayland (see issues).

2. Sign in — bring three things

1Password sign-in needs (a) your sign-in address (usually my.1password.com), (b) your email, and (c) your Secret Key (the 34-character key from your Emergency Kit) plus your master password. First-time users: create the account at 1password.com first and save your Emergency Kit PDF somewhere safe — if you lose the Secret Key, 1Password cannot recover your vault. That’s by design.

3. The 3 things you need to know

• Unlock once, use everywhere. Unlock the desktop app and the browser extension unlocks with it — the app and extension share lock state over an encrypted connection (on Linux, via the kernel keyring). This is the feature that makes 1Password feel magical, and it’s the one that breaks most often on Linux (see issues).
• Autofill lives in the browser. Install the official 1Password extension in Chromium or Firefox, then right-click the extension icon → Settings → General → turn on “Integrate this extension with the 1Password desktop app.” After that, the inline menu appears in login fields automatically.
• Passkeys and 2FA are built in. 1Password saves and uses passkeys, generates TOTP codes, and its Watchtower dashboard flags reused/weak/breached passwords. The SSH agent (Settings → Developer) turns your vault keys into an SSH agent at ~/.1password/agent.sock.

4. Config location

~/.config/1Password/. Browser-native-messaging plumbing lives in ~/.config/google-chrome/NativeMessagingHosts/ or ~/.mozilla/native-messaging-hosts/; the system-wide custom-browser allowlist is /etc/1password/custom_allowed_browsers.

5. CLI pro tip

In the desktop app, Settings → Developer → Integrate with 1Password CLI, and Settings → Security → Unlock using system authentication. After that, op vault list just works — it authenticates through the unlocked app instead of expiring session tokens, and the 1Password SSH agent (~/.1password/agent.sock) can replace ssh-agent entirely.

Common issues & fixes

The browser extension doesn’t unlock when the desktop app unlocks

Fix: This is the #1 Linux issue and it’s almost always sandboxing. If your browser is a Flatpak or Snap, it can’t reach 1Password’s native-messaging host, so unlock-sync silently fails. 1Password’s own support team confirms: install the browser from a native package (not Flatpak/Snap) and integration works. On Omarchy that’s the default anyway — just don’t add a Flatpak browser on top and expect 1Password to follow. (1Password Community; Chrome/Brave thread)

Your browser isn’t on 1Password’s official supported list (Vivaldi, Zen, Floorp, etc.)

Fix: Add the browser’s binary name to the system allowlist, then restart both:

sudo mkdir -p /etc/1password
echo "vivaldi-bin" | sudo tee -a /etc/1password/custom_allowed_browsers
sudo chown root:root /etc/1password/custom_allowed_browsers && sudo chmod 644 /etc/1password/custom_allowed_browsers

Replace vivaldi-bin with your browser’s actual binary (zen-bin works for Zen). This is the documented workaround from 1Password support. (Vivaldi forum)

Copy-paste from 1Password behaves oddly on Hyprland/Wayland

Fix: Two separate quirks. First, 1Password now marks copied values as sensitive so clipboard daemons should skip them — if yours doesn’t, that’s the manager’s bug, not 1Password’s; try the beta channel (omarchy pkg add 1password-beta), which has carried clipboard fixes. Second, on pure Wayland the safest path is avoiding the clipboard entirely: use the browser extension’s autofill, or drag-and-fill from the desktop app. (1Password Community; Hyprland issue #6443)

Fingerprint / system-auth unlock doesn’t work, or 1Password demands the full master password every time

Fix: On Linux, “Unlock using system authentication” (Settings → Security) goes through PAM/polkit — you need a working polkit authentication agent, and on minimal window managers one may not be running. Also expect this: after a restart of the app or the computer, 1Password always requires the account password first; system auth only kicks in for subsequent unlocks. Fingerprint-via-fprintd on Arch is a known rough edge with open support threads. (1Password Community)

On a fresh minimal Arch/Hyprland install, 1Password’s secret storage misbehaves

Fix: Install gnome-keyring and libsecret, and make sure the keyring unlocks at login via PAM — the same stack Omarchy-adjacent Hyprland setups use for everything else. Community threads document this as the fix for 2FA-saving failures on Arch. (example dotfiles setup)

Pairs well with / If you hate this, try

Pairs well with

• 1password-cli — the op command for terminal workflows, scripts, and secret injection (omarchy pkg add 1password-cli). 1password-beta — the beta channel for early fixes, maintained by 1Password in the AUR (omarchy pkg add 1password-beta). A native (non-Flatpak) Chromium or Firefox.

If you hate this, try

• Bitwarden — the honest free alternative (see below).

Comparison: 1Password vs Bitwarden vs KeePassXC

One-line verdict: 1Password wins on polish and integrations; Bitwarden wins on price — and its free tier is genuinely full-featured, not a trial with a countdown.

How to switch from 1Password to Bitwarden (~15 minutes)

1. Export from 1Password: open the desktop app → ⋮ menu → Export → choose your account → save the .1pux (or unencrypted CSV — delete it immediately after).
2. Import into Bitwarden: web vault → Tools → Import → select “1Password (1pux)” or “1Password (csv)” → upload.
3. What doesn’t transfer: file attachments on some export formats, some custom field types, and your 1Password Secret Key setup (Bitwarden uses email + master password + optional 2FA instead).
4. Re-point your browser extension and turn off 1Password’s “integrate with browser” to avoid both extensions fighting over login fields.