Troubleshooting

No identities appear

Confirm the environment points at Lanyard, not an old forwarded path. Then check whether the local 1Password socket exists or register the incoming remote socket explicitly.

Your terminal multiplexer sees an old socket

This is the problem Lanyard removes: update the long-running session once in Zellij, tmux, or your multiplexer of choice so SSH_AUTH_SOCKpoints at the stable Lanyard socket. Future forwarded agents change behind that address.

Git says “agent refused operation”

• Confirm the configured user.signingkey matches an identity fromssh-add -L.
• Unlock or approve the relevant upstream agent.
• Use status --json to inspect current candidate order and reachability.
• Check whether a 30-second approval timeout elapsed.

Forwarded agent disappeared

Temporary OpenSSH sockets vanish when their connection closes. Lanyard removes dead candidates from active routing; reconnect or explicitly unregister stale paths if you want to clean the status view immediately.

Collect diagnostics

Redact usernames, socket paths, public-key comments, and host details before posting logs publicly. Public keys are not secret, but they are identifiers.