Protect what matters – even after you're gone. Make a plan for your digital legacy today.
1Password Oddities
These have been issues for a while, but re-testing them today, I'm using "1Password for Mac 8.11.22 (81122027)", Google Chrome "144.0.7559.59", and 1Password extension "8.11.27.2". --- Is there a reason why I have to use my mouse and keyboard on web-pages that use XHTML? https://craig.dev/misc/1Password/2023-12-12-xml/ If I select either the username or password field (I'm using autofocus on the username field, but this isn't necessary)... the 1Password icon appears (good), but if I click on it with the mouse, then it just disappears... so now I need to use the [down arrow] button on my keyboard to show the 1Password account selection menu... but, if I press the [down arrow] a second time (i.e. to make a selection), then the 1Password select menu disappears, so I need to go back to using my mouse to select the account I want. This seems to be due to the use of `Content-Type: application/xhtml+xml`, you can change back to normal (error tolerant) HTML with the "change" link on this page. --- Also, because I have a `Permissions-Policy` header on my websites, where I set `ch-ua-high-entropy-values=()` to disable the getHighEntropyValues API, I get this error in the Google Chrome Developer tools: Permissions policy violation: Collection of high-entropy user-agent client hints is disabled for this document https://craig.dev/misc/1Password/2026-01-11-high-entropy/ --- Also, on either of these pages, you can see the scrolling issue... as in, when you try to scroll the page, the 1Password button remains fixed in position relative to the browsers window (not keeping track of the username/password field location): I suspect it's related to the setButtonStyles() function in "injected.js", which is using `button.style.position = "fixed"`... I'm not sure on the details, but if I was looking into this, I'd start by considering the use of position absolute. --- Also, every time I select a username/password field, and then use the down arrow so 1Password opens the select field, I get a warning in the Google Chrome Developer tools: Added non-passive event listener to a scroll-blocking 'wheel' event. Consider marking event handler as 'passive' to make the page more responsive. --- And finally, following on with the SMS verification codes discussion, what HTML should I be using on my SMS one-time-code fields, so I can tell 1Password to ignore this field (i.e. so the browser can offer the value from the SMS message)? I'm currently using: <input name="code" id="sms_code" required="required" autofocus="autofocus" autocomplete="one-time-code" type="text" inputmode="numeric" size="9" maxlength="7" value="">
Reference for Private vault copied from GUI doesn't work in CLI
I use the `op` cli with a personal/family account. When I right click a password/key in the GUI in my Private account and selects "Copy Secret Reference", the reference starts with "op://Private". If I tried to read the reference using `op read` it fails with [ERROR] 2025/08/08 15:24:36 could not read secret op://Private/{Item}/{Field}: could not get item Private/{Item}: "Private" isn't a vault in this account. Specify the vault with its ID or name. So I have to replace the vault segment it with "Personal" or the vault reference hash to make it work with `op`. This is really inconvenient. Why is this happening? Is there anything I can do to fix it? (The "Private" vault can't be renamed.)
AWS completer with OP cli
Recently I was trying to set up my environment and noticed that I could not get aws completer to work. After some triaging, I was able to track it down to OP CLI. If I disabled it .zshrc, Completer worked as expected. Once re-enabled, it no longer worked. I am currently using Ghostty with ZSH as my terminal. Thoughts on what I can do to get the two working together? Thanks
CLI can't connect
[ERROR] 2025/12/17 14:09:48 connecting to desktop app: 1Password CLI couldn't connect to the 1Password desktop app. To fix this, update the 1Password app to the latest version and restart the app. If you're still having trouble, visit https://developer.1password.com/docs/cli/app-integration#troubleshooting for more help. CLI cant connect to the desktop app anymore. Opening the desktop app I get prompted with this message Your saved data appears to be newer than this version of 1Password can use. Please update 1Password to its latest version. Contact support@1password.com for help. I've since attempted to reinstall the desktop app using the latest release, as well as the beta release, but both versions still give me the error above. this is 8.11.22 and 8.11.22-26 Macbook M3 Pro OS - Sequoia 15.6.1 CLI version - 2.32.0
ssh agent and ansible 12 prompting incessantly
I've been using the SSH Agent in 1Password for a couple of years now, with very little trouble. This includes lots of SSH to individual machines as well as a fair amount of ansible scripting using versions prior to 12 and run directly from Terminal. Recently, I did a `brew upgrade` and ended up with Ansible 12. After that, it has become commonplace that ansible scripts run on my local machine and talking to nearby devices over the network result in 1passwd SSH agent prompting for every...single...command. I rolled back to ansible 10 (11 not available directly in Brew any longer) and the behavior returned to normal: prompting at the outset of my ansible script and not again until the next time I run a script. Running Ansible (as opposed to directly sshing in Terminal) has always prompted at the run, and usually for each individual destination machine, but that has been it. With the change to Ansible 12, the prompting from the SSH agent in 1password is now such that it is not usable. For the time being, I can roll back to ansible 10, but that won't be the case forever. Does anyone else have experience with this? Any recommendations for either diagnostics or solutions other than just disabling 1password's otherwise-highly-useful SSH Agent?Cannot find "Destinations" tab for mounting secrets to local .env files
I am trying to use the feature "Access secrets from 1Password through local .env files" but I cannot find the "Destinations" tab. What I have done: Enabled "Show 1Password Developer experience" in Settings > Developer Enabled "Record and display activity" I can see and use the AWS Secrets Manager integration What I expected: According to the documentation, there should be a "Destinations" tab that allows me to mount secrets to a local .env file. What I see: The "Destinations" tab does not appear anywhere in the interface. I only see the AWS Secrets Manager integration option. Environment: 1Password version: Latest OS: Windows Account type: Individual Could you please help me understand how to access the Destinations feature, or let me know if this feature has been moved or deprecated? Thank you.
SSH agent requires restart between every GitHub request
I've been using the 1Password SSH agent to sign commits and authenticate with GitHub for months without any issues. Today, I started experiencing intermittent SSH timeouts when trying to pull, fetch, or push: ssh: connect to host github.com port 22: Connection timed out fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. At first I assumed this was a GitHub outage, but I noticed that when 1Password prompted me to approve the SSH key, the request would succeed. After a while, the timeouts would return. I changed "Remember key approval" from 12 hours to "until 1Password quits." This helped, but now I have to restart 1Password and re-approve the key between every single Git request, otherwise it times out again. Environment: Windows 11 Affects Git CLI, Git Fork, and VS Code Commit signing with the same key still works fine What I've tried: Changing "Remember key approval" to "until 1Password quits" Restarting 1Password (temporarily fixes it for one request) Restarting my computer Has anyone else run into this? Any suggestions would be appreciated.Service Degradation (Resolved)
Update: This issue has been resolved. Carry on. ------- Hi all, We are seeing a service degradation that’s impacting sign-ins, SSO, MFA, and accessing items across the board. The team’s already digging into what’s going on, and you can follow updates as they’re posted here: https://status.1password.com/incidents/hxqx48n0hpg6 Thanks Phil
