Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Helper to interface with Windows ssh-agent.exe service from Windows Subsystem for Linux (WSL)
| Date | Stars |
|---|---|
| 2026-07-31 | 569 |
| 2026-08-05 | 569 |
| 2026-08-18 | 571 |
| 2026-08-25 | 572 |
| 2026-08-30 | 573 |
| 2026-09-01 | 572 |
| 2026-09-20 | 572 |
Today
— stars today
This week
— stars this week
This month
+1 stars this month
Momentum
0.0
growth rate 0.00%/day
<h1>
<img src="docs/ssh.svg" style="vertical-align:middle; width:8%" align="absmiddle"/>
<span style="vertical-align:middle;"> wsl-ssh-agent</span>
</h1>
# IMPORTANT NOTE ON PROJECT HISTORY
This project was started at the time when WSL2 did not exist and Microsoft just implemented AF_UNIX socket support. Today it is useful only when WSL1 is being required - which is really rare. Sharing Windows side ssh-agent with WSL2 does not need `wsl-ssh-agent.exe` at all! Please, read on next section on how to setup WSL2 and only continue after that if you really working with WSL1.
## WSL2 compatibility
At the moment AF_UNIX interop does not seem to be working with WSL2 VMs. Hopefully this will be sorted out eventually. Meantime there is an easy workaround (proposed by multiple people) which does not use `wsl-ssh-agent.exe` and relies on combination of linux socat tool from your distribution and [npiperelay.exe](https://github.com/jstarks/npiperelay). *For example* put `npiperelay.exe` on drvfs for interop to work its magic (I have `winhome ⇒ /mnt/c/Users/rupor`, copy [wsl-ssh-agent-relay](docs/wsl-ssh-agent-relay) into your `~/.local/bin directory`, and add following 2 lines to your .bashrc/.zshrc file:
```bash
${HOME}/.local/bin/wsl-ssh-agent-relay start
export SSH_AUTH_SOCK=${HOME}/.ssh/wsl-ssh-agent.sock
```
**NOTE:** If you are having issues using `wsl-ssh-agent-relay` with systemd try adding `:WSLInterop:M::MZ::/init:PF` to `/usr/lib/binfmt.d/WSLInterop.conf`. For example (thanks to [rkl110](https://github.com/rkl110) - [Microsoft/WSL - Issue 8843](https://github.com/microsoft/WSL/issues/8843)):
```bash
sudo sh -c 'echo :WSLInterop:M::MZ::/init:PF > /usr/lib/binfmt.d/WSLInterop.conf'
```
Alternatively if you prefer to directly use systemd support in WSL2 /etc/wsl.conf:
```ini
[boot]
systemd = true
```
you could create wsl-ssh-agent.service unit in `/usr/lib/systemd/user`, something similar to:
```ini
[Unit]
Description=Windows SSH Agent Proxy via npiperelay
StartLimitIntervalSec=0
[Service]
Delegate=true
Type=exec
KillMode=process
ExecStart=/usr/bin/socat UNIX-LISTEN:'/run/user/<user id, usually 1000>/wsl-ssh-agent.sock',fork EXEC:'/home/<user name>/winhome/.wsl/npiperelay.exe -ei -s //./pipe/openssh-ssh-agent',nofork
[Install]
WantedBy=default.target
```
and then enable it:
```bash
systemctl --user daemon-reload
systemctl --user enable --now wsl-ssh-agent.service
export SSH_AUTH_SOCK=${XDG_RUNTIME_DIR}/wsl-ssh-agent.sock
```
You *really* have to be on WSL 2 in order for all of this to work - if you see errors like `Cannot open netlink socket: Protocol not supported` - you probably are under WSL 1 and should not use this workaround. Run `wsl.exe -l --all -v` to check what is going on. When on WSL 2 make sure that npiperelay.exe is on windows partition and path is right. For convenience I will be packing pre-build npiperelay.exe with wsl-ssh-agent. Please also ensure that `socat` is installed: `sudo apt install socat`.
**NOTE:** You may be running Linux distribution with OpenSSH version more recent than your Windows host has out of the box. Presently Ubuntu 22.04 and Arch both demonstrate this - communication with ssh-agent will fail. In such cases please visit [Windows OpenSSH](https://github.com/PowerShell/Win32-OpenSSH) development and update your Windows OpenSSH with latest release.
## Helper to interface with Windows ssh-agent.exe service from WSL1 (replacement for ssh-agent-wsl).
[](https://github.com/rupor-github/wsl-ssh-agent/releases)
Windows has very convenient `ssh-agent` service (with support for persistence and Windows security). Unfortunately it is not accessible from WSL. This project aims to correct this situation by enabling access to SSH keys held by Windows own `ssh-agent` service from inside the [Windows Subsystem for Linux](https://msdn.microsoft.com/en-us/commandline/wsl/about).
My firstExcerpt of 14,877 characters
Read on GitHub
91
Oliver Kopp · University of Hamburg · Germany
2
1
1
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
Not classified yet. Classification runs as part of npm run ingest.