Desktop app constantly prompting for SSH Key acceptance

Which Bitwarden app is your issue or question about?

3 - Desktop App

Bitwarden App Version

2026.8.0

Operating System

05 - Linux / Windows

Where is your vault hosted?

Bitwarden (default)

Description

I am not sure if it is me or not, but when I use Bitwardens SSH Agent, something happens at some point which I cannot pinpoint, that when I unlock the agent it re-prompts me to see if I want to authorize the key again (even if the client app is closed). I am only using one SSH client app so not sure if this is the client app or a BW problem. For me it is occuring across Linux and Windows. Just thought I would ask the community to see if anyone else is having this issue. To resolve, I quit BitWarden and then restart it, and it is fine, until some point in the future. When it goes wrong, it stays wrong.

OK - I think I can make this fail for me, using a different app.

My Configuration

  • Linux Flatpak BitWarden v2026.8.0 (Happens with Windows as well but I got it to fail here first)
  • SSH Agent enabled in BW with prompt Always
  • Pin unlock
  • Application used: ssh on terminal

Process

  1. Quit Bitwarden
  2. Open Bitwarden
  3. Unlock with master password
  4. Open terminal and SSH to host that requires key
  5. Authorize key usage
  6. Disconnect from server (this is not required as it happens even if connected)
  7. Lock all vaults in BW and close (it minimizes)
  8. SSH to the server again
  9. Bitwarden will pop up and prompt for pin. Do this
  10. Authorise the connection
  11. Lock all vaults
  12. Minimize
  13. Open Bitwarden
  14. Unlock with pin
  15. It will now prompt to authorize the key even though there is nothing asking for it.
  16. (I kept the connection open to the server)

I will check with Windows to see if this is the exact same scenario where this happens.

While the steps 11,12,13,14 are listed, I have been able to get it to fault (at least when it is failing by doing 11 then 14).

The only to fix this is to quit Bitwarden and start again

OK - I can get this to fault on Windows as well. I will log an issue on Github.

Basically

  1. Have prompt for authorization as Always
  2. Have the vault lock after awhile (simulate with lock vault)
  3. Lock vault
  4. minimize vault
  5. Create an SSH connection
  6. Authorize
  7. Now when you lock/unlock it will continue to prompt.

So now two reasons to not lock you vault (against good practice)

  1. Annoying popup that should not be there
  2. Forgetting where you were (Folder/item) before the lock.