Sourcetree Support for Built-in Windows SSH Agent
Asked by brandon_liles:

Since Windows 10 1803, a built-in/optional OpenSSH implementation is included with Windows, including a SSH agent service. I've configured git to use this OpenSSH by adding this to my .gitconfig:

\[core\]  
sshCommand = "C:/Windows/System32/OpenSSH/ssh.exe"

Sourcetree however, seems to only want to use either Pageant or the OpenSSH agent bundled with Git. Anyone know of a workaround, or do we just have to wait for Sourcetree to support the built-in OpenSSH implementation?


Answers:
author: minnsey
body: Hi  

We have prototyped using the built in OpenSSH but ran into some issues around make sure it was available and running. We continue to monitor it and work on it, but it is not yet a roadmapped feature.

comments: author: David
body: It's been a couple of years, has there been any progress on this feature?

I'd really like to get ride of putty and the custom OpenSSH ssh-agent.


author: Ryan Taylor
body: [@minnsey](/t5/user/viewprofilepage/user-id/502201)Has there been any progress on this?  

When I configure SourceTree to use OpenSSH it appears to start a new ssh-agent each time SourceTree is started and I receive the following error:

![2023-08-14_8-29-24.png](https://community.atlassian.com/t5/image/serverpage/image-id/274980i3B2D58CA133991C4/image-size/large?v=v2&px=999 "2023-08-14_8-29-24.png")

SourceTree is not the only way in which our teams interact with git via SSH. We also use the git cli directly, vscode, visual studio, Git Kraken, among others. It would be immensely helpful if SourceTree for Windows could use the same OpenSSH agent that Bitbucket's [own documents mention](https://support.atlassian.com/bitbucket-cloud/docs/set-up-personal-ssh-keys-on-windows/#Windows-OpenSSH-users).


author: Leons
body: [@Ryan Taylor](/t5/user/viewprofilepage/user-id/5239046) When your OpenSSH of windows setting is ok, then you no need the ssh client of SourceTree. Disable it and use the system git.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/276809iAA4B8E401FDF36C0/image-size/large?v=v2&px=999 "image.png")![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/276810iC0FD36EB76AAD6C6/image-size/large?v=v2&px=999 "image.png")


author: Ryan Taylor
body: [@Leons](/t5/user/viewprofilepage/user-id/817057)when I do that, SourceTree is then configured to use PuTTY rather than OpenSSH and I receive errors on fetch and pull.

My OpenSSH configuration works flawlessly with

* git bash
* git from cmd/powershell
* git from vscode
* git from visual studio
* [fork](https://git-fork.com/)
* [GitKraken](https://www.gitkraken.com/)

The only tool chain that seems to have issues with Windows' built-in OpenSSH is SourceTree.


author: Ryan Taylor
body: SourceTree is not the only way in which our teams interact with git. We also use the git cli directly, vscode, visual studio, among others. It would be immensely helpful if SourceTree for Windows could use the same OpenSSH agent that even your [own documents mention](https://support.atlassian.com/bitbucket-cloud/docs/set-up-personal-ssh-keys-on-windows/#Windows-OpenSSH-users).

This could simplify setup.


author: Shawn Zivontsis
body: I was able to accomplish this with the newly released winssh-pagent tool by setting Sourcetree to use Pageant auth and unchecking the "Start agent" box. See: <https://github.com/ndbeals/winssh-pageant>


author: David A?ez
body: Greetings!

Is this feature still considered for a future release?

In my new job I started using SourceTree, since it is the division policy, and I like it so far. However, I wish it could use Windows SSH-Agent, which I already successfully configured for the few instances when I do manual git commands.


author: TeiTec
body: Hi,

Is there meanwhil an update when the feature will be available or at least on the roadmap?