Protect what matters – even after you're gone. Make a plan for your digital legacy today.
1Password on Flathub
Since the recent https://1password.community/discussion/comment/615214/#Comment_615214 would be, time to publish 1Password on https://flathub.org/home. Flathub is the best known Flatpak package store, so it would be a good idea to public 1Password on it, and it is easier to find Flatpak apps directly from it, since users expect most Flatpak apps to be there. Here is the guide on how to publish on Flathub: https://github.com/flathub/flathub/wiki/App-Submission 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided
Feature Request: Show Original Contributor of Items in Shared Family Vaults
Summary Please add a built-in way to display who originally created or contributed an item to a shared vault in 1Password Family. Problem In shared family vaults, it is currently not possible to see who an item originally belongs to once it has been shared. This makes it unclear who owns a specific account, even though the item is visible to everyone in the family. As a workaround, we manually add tags with the name of the person who created or contributed the item. This allows sorting and filtering by owner, but it is manual, error-prone, and easy to forget. Proposed Feature Display non-editable metadata such as: “Contributed by: Name” or “Original owner: Name” This information should remain visible in the item details after sharing or moving an item into a shared family vault. Benefit This makes it easy to understand who an account actually belongs to, even when it is shared for convenience. It improves clarity in family vaults, avoids confusion, and removes the need for manual tagging. Reference Apple Passwords already shows this information for shared items using labels like “Contributed by: Name”, which provides clear ownership at a glance.
Use TPM 2.0 PCR binding to allow password-less unlock after reboot on Linux
The Problem: Windows/macOS: Users can reboot and immediately use Windows Hello or Touch ID to unlock. The Master Password is rarely needed. Linux: Even with "System Authentication" enabled, we are forced to type the full Master Password at least once after every reboot or app restart. The Proposal: I would love to see 1Password for Linux implement native TPM 2.0 support to securely store the vault decryption secret, bound to the system's hardware state. Since modern Linux distributions (like Arch, Fedora, Ubuntu) now have mature TPM support (e.g., via systemd-cryptenroll), the infrastructure is ready. How it could work: 1.Secret Sealing: 1Password could seal the necessary decryption key into the TPM chip. 2.PCR Binding: Bind this key to specific Platform Configuration Registers (PCRs), such as PCR 7 (Secure Boot state) and PCR 0 (Firmware). The Result: On boot, if the system hasn't been tampered with (Secure Boot is valid), the TPM releases the key, and 1Password unlocks automatically—or just asks for a fingerprint—without needing the Master Password. Why this matters: Parity: It brings the Linux client up to par with the "magic" experience on other platforms. Security vs. Convenience: It encourages users to set incredibly long, complex Master Passwords because they won't have to type them daily. I know many power users in the Linux community are already using TPM for disk encryption (LUKS). It would be amazing to see 1Password leverage this same hardware capability. Does anyone else in the community want this? Please vote or comment if you do! Thanks1Password Beta + SSH Agent + Hyprland
I’m seeing an issue on 8.11.12_26.BETA where the SSH agent window opens at only ~400x100, making it difficult to use. This problem does not occur on earlier builds — after downgrading to 8.11.10-32.BETA, the window renders normally and everything works fine again. I also noticed a mention of a fix in 8.11.12_26.BETA-26, which seems like it might be related and potentially introduced a regression. [Fixed] We’ve fixed an issue that prevented rich SSH and CLI prompts from appearing on Wayland. Environment: Omarchy v3.0.2 Hyprland 0.51.1 (Wayland) Linux 6.16.8-arch3-1 Happy to provide logs or run additional tests if helpful. Thanks for looking into this! Omarchy issue for additional context: https://github.com/basecamp/omarchy/issues/2016
Mouse/window handling issues on Ubuntu
Hi, my 1password developed a weird window mgmt issue -- it's as if all mouse left button events are being remapped to right button events for window mgmt. So e.g. clicking on the close 'x' button on the window doesn't close the app but produces the context menu. Mouse buttons within the app itself work as they should, it's only the window mgmt that's affected. 1password ver 8.11.16 Ubuntu 25.10 Weird bug?
Latest beta doesn't show in app tray
The latest 1Password beta appears to have an error on launch and won't show in the system tray in Linux. All previous betas did not have this issue and the current release version also doesn't have this issue so it appears to be a regression. Version: 1password-beta-8.11.16_30 Console output when launching 1Password: INFO 2025-10-16T07:09:49.078+00:00 ThreadId(34) [1P:op-settings/src/store/json_store.rs:75] Settings file created @ 2024-10-23 19:22:28.731374786 UTC and last modified @ 2025-10-16 07:04:03.841979318 UTC INFO 2025-10-16T07:09:49.079+00:00 ThreadId(34) [client:typescript] Client starting. INFO 2025-10-16T07:09:49.137+00:00 ThreadId(34) [1P:op-localization/src/lib.rs:239] system locale detected as 'en-US' INFO 2025-10-16T07:09:49.137+00:00 ThreadId(34) [1P:op-localization/src/lib.rs:265] selected translations for EN_US based on detected locale en-US INFO 2025-10-16T07:09:49.137+00:00 ThreadId(34) [status:app/op-app/src/app.rs:1030] App::new(1Password for Linux/81116030 (EN_US), /home/<redacted-username>/.config/1Password) INFO 2025-10-16T07:09:49.139+00:00 ThreadId(34) [1P:data/op-db/src/common/mod.rs:186] Core DB Integrity Check Succeeded INFO 2025-10-16T07:09:49.139+00:00 ThreadId(34) [1P:data/op-db/src/core_db/db.rs:145] Starting Core DB at version: 46 INFO 2025-10-16T07:09:49.139+00:00 ThreadId(34) [1P:data/op-db/src/common/mod.rs:155] Core DB Table Integrity Check Succeeded INFO 2025-10-16T07:09:49.146+00:00 ThreadId(34) [1P:data/op-db/src/common/mod.rs:186] Resources DB Integrity Check Succeeded INFO 2025-10-16T07:09:49.146+00:00 ThreadId(34) [1P:data/op-db/src/common/mod.rs:155] Resources DB Table Integrity Check Succeeded INFO 2025-10-16T07:09:49.146+00:00 ThreadId(34) [1P:data/op-db/src/resources_db/db.rs:110] Starting Resources DB at version: 1 INFO 2025-10-16T07:09:49.146+00:00 ThreadId(34) [1P:ssh/op-ssh-config/src/lib.rs:380] agent not configured INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/google-chrome/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/google-chrome-beta/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/google-chrome-unstable/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/chromium/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/microsoft-edge-dev/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/vivaldi/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/vivaldi-snapshot/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.mozilla/native-messaging-hosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 ThreadId(34) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests. INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(31)) [1P:op-global-shortcuts/src/node.rs:38] Global shortcut registration is not available on this system. INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(25)) [1P:op-global-shortcuts/src/node.rs:38] Global shortcut registration is not available on this system. INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/google-chrome/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/google-chrome-beta/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/google-chrome-unstable/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/chromium/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/microsoft-edge-dev/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/vivaldi/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.config/vivaldi-snapshot/NativeMessagingHosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/<redacted-username>/.mozilla/native-messaging-hosts/com.1password.1password.json INFO 2025-10-16T07:09:49.149+00:00 runtime-worker(ThreadId(24)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests. INFO 2025-10-16T07:09:49.151+00:00 ThreadId(34) [1P:app/op-app/src/app.rs:1688] initializing Developer Environment mount handler INFO 2025-10-16T07:09:49.152+00:00 runtime-worker(ThreadId(27)) [1P:app/op-app-common/src/unlocked_session_keepalive.rs:70] Starting unlocked session keepalive INFO 2025-10-16T07:09:49.152+00:00 runtime-worker(ThreadId(27)) [1P:native-messaging/op-native-core-integration/src/lib.rs:428] Starting IPC listener on 1Password-BrowserSupport ERROR 2025-10-16T07:09:49.152+00:00 runtime-worker(ThreadId(3)) [1P:native-messaging/op-native-core-integration/src/lib.rs:618] Listener on SETTING_STATUS has been dropped, unable to communicate changes made to browser SLS setting ERROR 2025-10-16T07:09:49.152+00:00 ThreadId(34) [1P:ffi/op-core-node/src/lib.rs:558] Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) INFO 2025-10-16T07:09:49.153+00:00 runtime-worker(ThreadId(31)) [1P:native-messaging/op-native-core-integration/src/lib.rs:440] Active native core integration is awaiting messages INFO 2025-10-16T07:09:49.153+00:00 runtime-worker(ThreadId(27)) [1P:ssh/op-agent-controller/src/lib.rs:573] Starting filesystem watcher for SSH agent configuration directories... ERROR 2025-10-16T07:09:49.153+00:00 runtime-worker(ThreadId(27)) [1P:/mnt/ephemeral/builds/dev/core/core/ssh/op-agent-controller/src/lib.rs:574] Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) (node:18057) UnhandledPromiseRejectionWarning: ReferenceError: self is not defined at Object.<anonymous> (/opt/1Password/resources/app.asar/552.js:1:14) at Module._compile (node:internal/modules/cjs/loader:1714:14) at Module._extensions..js (node:internal/modules/cjs/loader:1848:10) at Module.load (node:internal/modules/cjs/loader:1448:32) at Module._load (node:internal/modules/cjs/loader:1270:12) at c._load (node:electron/js2c/node_init:2:17993) at TracingChannel.traceSync (node:diagnostics_channel:322:14) at wrapModuleLoad (node:internal/modules/cjs/loader:244:24) at Module.require (node:internal/modules/cjs/loader:1470:12) at require (node:internal/modules/helpers:147:16) (Use `1password --trace-warnings ...` to show where the warning was created) (node:18057) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) INFO 2025-10-16T07:09:49.351+00:00 runtime-worker(ThreadId(25)) [1P:app/op-app/src/app/backend/lock_screen.rs:96] System unlock is enabled: false INFO 2025-10-16T07:09:49.351+00:00 runtime-worker(ThreadId(25)) [1P:app/op-app/src/app/backend/lock_screen.rs:124] Sys auth status Disabled INFO 2025-10-16T07:09:49.537+00:00 1p-enable-crash-reporter(ThreadId(37)) [1P:op
1Password no longer offering to fill in locally hosted http service
On my local LAN, I have an instance of a news feed reader program, tt-rss, running. It's recently moved to new management after its original author dropped the open source project. As it's not externally accessible, I can't easily give it something like an LE SSL certificate, so it runs over plain HTTP. I run Ubuntu, and at the moment use the 1Password Beta 8.11.22.25 plugin in Firefox 145.0.2-canonical-002-1.0 snap, so due to the ongoing sandboxing issues, 1Password browser plugin cannot communicate with the local 1Password instance, and phones home to 1Password servers instead. The URL of the internal-only service is something like: http://ttrss.internal.external.tld.country/ ... and it resolves to something in RFC1918 range. When I tell the plugin to "Collect Page Structure", the JSON it returns is: { "unparsedUrl": "http://ttrss.internal.external.tld.country/", "title": "Tiny Tiny RSS : Login", "frames": [] } ... so it seems like 1Password browser plugin is not even giving me the option to ignore the HTTP warning (like it does on my Android device), rather it's fully blocking auto-fill from the page (why isn't it parsing the URL?)? At the moment, my workaround is to click on 1Password icon in browser, and them manually copy username and password. Is this a deliberate removal of support for autofill of HTTP support in latest versions? Could this perhaps still be supported for RFC1918 IPs?Wayland browser extension login issue
Recently I am not able to login to 1Password by clicking on the icon in Firefox. Instead of giving me a login screen, I get a popup with just the 1Password logo but no field to enter my password. This did used to work. If I open the app and login, then the browser extension works correctly. I am running Hyprland with Arch.
Feature Parity Request: Native "Generate Masked Email" Button (NordPass-style implementation)
Hi team, I am writing this as a paying customer of both 1Password and Fastmail. I recently migrated my entire workflow from NordPass to 1Password because, frankly, 1Password is the superior product in almost every way—except one. The Missing Feature: I need the ability to manually generate a Masked Email from within the 1Password app (Windows, Android, Web) without relying on the browser extension to "detect" an email field. The Context (The "Downgrade" Experience): In NordPass, "Email Masking" is a first-class citizen in the UI. I can open the desktop or mobile app, click "New Mask," and instantly have a private email address to use anywhere—whether I'm signing up inside a native Android app, filling out a paper form at a doctor's office, or dealing with a complex multi-page web form that your extension doesn't recognize. Currently, with 1Password, if the browser extension doesn't trigger the "Create Mask" bubble, I am stuck. I have to break my workflow, open Fastmail, navigate deep into settings, create a mask, and copy-paste it back. It makes the integration feel fragile and "browser-only." What I am asking for: I don't care if the backend is powered by Fastmail or a future native 1Password relay service. I just need a "Generate Masked Email" button inside the standard Item Editor on all platforms. Relevant Tracker IDs: I have done my research and believe this request maps to the following existing internal tickets. Please add my vote to them: PB-45537123 (UI path to manually create masks) PB-51907383 (Editing existing logins with masks) PB-49630961 (Mobile/Native app creation) IDEA-I-1983 (Desktop app manual generation) I moved to 1Password for a premium experience. Please close this gap so I don't have to miss the one thing NordPass actually got right. Thanks.