[Windows] Disabling ssh-agent still claims the socket

[jmigual]

Steps To Reproduce

1. Have version 2025.1.3 installed
2. Have OpenSSH agent enabled with some identities.
3. Uncheck the "Enable SSH agent" option in Bitwarden to disable the ssh agent
4. Run ssh-add -l to list the identities multiple times.

Expected Result

The agent should list my identities

Actual Result

I get an alternating output between:

> ssh-add -l
error fetching identities: agent refused operation

and

> ssh-add -l
4096 SHA256IDENTITY1 (none) (RSA)
2048 SHA256:IDENTITY2 .\default.pem (RSA)

This happens because the bitwarden ssh-agent is still claiming the \\.\pipe\openssh-ssh-agent socket even though I disabled the OpenSSH agent from Bitwarden.

Screenshots or Videos

No response

Additional Context

In my case I want to keep using the OpenSSH agent while having Bitwarden installed in my system for other log ins (I'm actually using the SSH compatibility of GPG agent). Shutting down Bitwarden is the only way I have to stop it from claiming the OpenSSH socket but I'd rather avoid that.

Operating System

Windows

Operating System Version

Windows 11 23H2 22631.4751

Installation method

Other

Build Version

Version 2025.1.3 SDK 'main (28c7e29)' Shell 33.2.1 Renderer 130.0.6723.137 Node 20.18.1 Architecture x64

Issue Tracking Info

• I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-17738

[Neonwarden]

Hi there,

This has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

[Sharparam]

On Linux the socket file gets created even if the SSH agent option is disabled, which feels like it could be adjacent to this issue?

Edit: Thread in the community about it: https://community.bitwarden.com/t/cannot-disable-ssh-agent/80176/2