Protect what matters – even after you're gone. Make a plan for your digital legacy today.
op CLI hangs on macOS Tahoe
macOS: 26.3.1 (a) (25D771280a) op version: 2.33.1 A few days ago, I upgraded the CLI from Homebrew, and all my Terminal sessions started to hang randomly from time to time. So I can no longer use it in the scripts anymore. I tested across multiple Terminals (Warp, macOS Terminal, iTerm) to make sure it wasn't isolated to a given terminal. I tried to research online, and I found https://github.com/openclaw/openclaw/issues/55459 which solved my problem, at least for now. I had to add that `export OP_CACHE=false`, so it seems that it wasn't related to my computer per se (to be clear, it is NOT about openclaw in my case) I can't find any thread in the forum, but ideally, `op` fixes the situation.
Getting rid of my individual account. I have a family account now.
I had an individual account, which I upgraded to a family account. ages ago. When logging into the program, it frequently shows both icons - I have nothing in that old individual account, but the program asks me for my old individual account's secret code (which I no longer have either) but I can't get rid of it. When doing a log in to the extension, when both icons are showing, it assumes I'm trying to open the individual account, and then fails, when I don't have for my old secret key. Then I have to click on the family icon, and then enter the password, and it opens, but it's an extra unnecessary step. How to get rid of it?
SSH Agent Forwarding to Remote Mac
Okay! I have a Mac Mini that I use as a home server (it was effectively free after trade ins of old stuff). I do have 1Password and its SSH agent running there for when i'm using it with a screen attached, but I'd like to be able to initiate 1Password requests when SSH'ed into the box as well so i can perform `git` operations in particular. I have tried https://developer.1password.com/docs/ssh/agent/forwarding/#remote-workstation and to an extent it works. ssh -A my_name@macmini.local cat ~/.ssh/config # Output, showing we are trying to force using SSH_AUTH_SOCK # Match host * exec "test -z $SSH_TTY" # IdentityAgent "~/Library/Group Containers/2BUA8C4S2C.com.1password/t/agent.sock" echo $SSH_AUTH_SOCK # /Users/my_name/.ssh/agent/s.czyqavwOqO.sshd.RviXimjiEr So I can see that I'm getting some kind of agent socket attached appropriately. I've configured the `.ssh/config` to not use the IdentityAgent when over SSH (it's not commented out in the actual file, just commented here for display purposes in the code block). However, when trying to run a git command, it's like SSH doesn't even try to use the auth socket for pulling data and `ssh-add -l` is equally unhelpful. ssh-add -l # The agent has no identities. git pull # git@github.com: Permission denied (publickey). # fatal: Could not read from remote repository. # Please make sure you have the correct access rights # and the repository exists. I am sure I'm just missing a configuration of some kind somewhere but I am at a loss for what it could be. Happy to provide other debug information from either the host or the remote Mac mini as needed.SSH agent isn't working (Windows 11)
I can't use my vault's SSH keys on my terminal. I've reinstalled multiple times and followed the https://developer.1password.com/docs/ssh/get-started/, but I can't make it work correctly. My 1Password config is set up as follows: I've disabled the OpenSSH Authentication Agent (the screenshot is in spanish) My ~/.ssh/config file: Host * IdentityAgent "~/.1password/agent.sock" My ~/.gitconfig file: [core] sshCommand = ssh.exe autocrlf = input [user] email = {email} name = {user} signingkey = ssh-ed25519 AAA[...] [gpg] format = ssh [gpg "ssh"] program = C:\\Users\\{user}\\AppData\\Local\\1Password\\app\\8\\op-ssh-sign.exe [commit] gpgsign = true Whenever I run ssh-add -L my vault's SSH keys are shown, but I can't seem to make it work with GitHub or connect to any SSH connection. ❯ ssh-add -L ssh-ed25519 AA[...] Authentication & Signing (Git) ssh-ed25519 AA[...] Authentication ❯ ssh -Tv git@github.com OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2 debug1: Reading configuration data C:\\Users\\{user}/.ssh/config debug1: C:\\Users\\{user}/.ssh/config line 1: Applying options for * debug1: Connecting to github.com [140.82.116.4] port 22. debug1: Connection established. debug1: identity file C:\\Users\\{user}/.ssh/id_rsa type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_rsa-cert type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_ecdsa type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_ecdsa-cert type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_ecdsa_sk type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_ed25519 type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_ed25519-cert type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_ed25519_sk type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_ed25519_sk-cert type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_xmss type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_xmss-cert type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_dsa type -1 debug1: identity file C:\\Users\\{user}/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_for_Windows_9.5 debug1: Remote protocol version 2.0, remote software version 133e47a51 debug1: compat_banner: no match: 133e47a51 debug1: Authenticating to github.com:22 as 'git' debug1: load_hostkeys: fopen C:\\Users\\{user}/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts2: No such file or directory debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ssh-ed25519 debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: SSH2_MSG_KEX_ECDH_REPLY received debug1: Server host key: ssh-ed25519 SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU debug1: load_hostkeys: fopen C:\\Users\\{user}/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts2: No such file or directory debug1: Host 'github.com' is known and matches the ED25519 host key. debug1: Found key in C:\\Users\\{user}/.ssh/known_hosts:3 debug1: ssh_packet_send2_wrapped: resetting send seqnr 3 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: ssh_packet_read_poll2: resetting read seqnr 3 debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: get_agent_identities: ssh_get_authentication_socket: No such file or directory debug1: Will attempt key: C:\\Users\\{user}/.ssh/id_rsa debug1: Will attempt key: C:\\Users\\{user}/.ssh/id_ecdsa debug1: Will attempt key: C:\\Users\\{user}/.ssh/id_ecdsa_sk debug1: Will attempt key: C:\\Users\\{user}/.ssh/id_ed25519 debug1: Will attempt key: C:\\Users\\{user}/.ssh/id_ed25519_sk debug1: Will attempt key: C:\\Users\\{user}/.ssh/id_xmss debug1: Will attempt key: C:\\Users\\{user}/.ssh/id_dsa debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: C:\\Users\\{user}/.ssh/id_rsa debug1: Trying private key: C:\\Users\\{user}/.ssh/id_ecdsa debug1: Trying private key: C:\\Users\\{user}/.ssh/id_ecdsa_sk debug1: Trying private key: C:\\Users\\{user}/.ssh/id_ed25519 debug1: Trying private key: C:\\Users\\{user}/.ssh/id_ed25519_sk debug1: Trying private key: C:\\Users\\{user}/.ssh/id_xmss debug1: Trying private key: C:\\Users\\{user}/.ssh/id_dsa debug1: No more authentication methods to try. git@github.com: Permission denied (publickey). One thing I noticed is that the folder .1password with the agent.sock file is not being created on my %USERPROFILE% folder. ❯ cd ~ && lsd -la | findstr ".1password" {empty} I installed lsd (chocolatey) on windows btwFailed to copy secret reference
When I right-click on a password and choose "Copy Secret Reference" , 1Password complains with "Failed to copy secret reference" at the bottom of the screen This happens on this particular entry, I tried a couple other Logins and I can Copy Secret Reference just fine. So what can cause this "Failed to copy secret reference" ? I'm using 8.11.1 on macOS Sequoia 15.5
1Password Environments issue with VSCode and Claude Code Extension
I've noticed a curious issue in testing 1Password Environments in a repository where I'm editing with VSCode and using the Claude Code extension in VSCode. Since enabling 1P Environments, I've noticed that the Source Control sidebar gets stuck refreshing Git Status, and Claude Code slows or stalls. Running Claude Code outside of VSCode works fine (as does using Git in Terminal, and so I wonder if this is a VSCode issue? I have the VSCode 1Password extension, as well as the Claude Code for VSCode extension, among others. Happy to provide other details if you can let me know what would help.[BUG REPORT] Two issues when editing multiple password fields
There are two issues with when editing multiple password fields of an item in 1Password. 1Password for Mac 8.12.2 81202037, on PRODUCTION channel Issue 1 When filling in multiple password fields below each other, I copy-past values from another application. When coming back to 1Password, the focus between password field items start to flicker. This is hard to stop and very annoying. You see this issue occur at 45 seconds into YouTube video 1Password UI Issues. Issue 2 Every time the password field gets focus, a "Generate a New Password" popup is shown below. This popup block direct access to the item below. This is very annoying. In YouTube video 1Password UI Issues, you see multiple password fields below each other in a single section. When I click on the input field of "Item 3" and paste a password value in the field, I want to be able to directly click on input field of "Item 4", which I cannot do because the annoying "Generate a New Password" popup is blocking direct access to this. I absolutely do NOT like these type of popups. They are frustrating and distracting. I have not asked for this "feature" and I want an option to disable this. I much more prefer a dedicated button in 1Password to generate a password. That way, I can choose myself when I actually want to generate a password in the password field that I have in focus. Don't annoy users with feature you think they like. Give users an option to disable/hide these unwanted UI features.1Password Connect Doesn't Appear to Sync Permissions
After submitting 1Password Connect Token Permissions Don't Appear to be Granular | 1Password Community , I update the permissions for the Access token for my dev environment. I then waited, and restarted the onepassword-connect deployment in my Kubernetes instance, which synced (verified in the 1PW UI under "Sync activity"). I did this twice. Despite the token having read/write access to the vault now, and being synced multiple times, when I apply terraform in that environment, and the onepassword terraform provider attempts to create a new entry, I see: Error creating 1Password item, got error failed to create item using connect: status 403: Authorization: token does not have permission to perform create on vault [redacted] Is there an additional action required to allow these permissions to sync?
