alvinunreal/openpets

Will re-release new version, to allow binding on non-localhost IPs - that's the only way here, you will need to bind and than configure in opencode WIN_HOST as IPC

Here from WSL
```log
~/.config/opencode $ cat /mnt/c/Users/***/AppData/Roaming/OpenPets/runtime/ipc.json
{
"protocolVersion": 1,
"protocol": "openpets-ipc",
"endpoint": "tcp://127.0.0.1:37645",
"token": "cRsqcUOgN-ibAWnDWSgmlr7DIDIsnbeypmUcZyslE_0",
"appVersion": "2.0.7",
"pid": 14764,
"platform": "win32"
}
~/.config/opencode $ nc -vz 127.0.0.1 37645
nc: connect to 127.0.0.1 port 37645 (tcp) failed: Connection refused
~/.config/opencode $ ip route show default | awk '{print $3}'
172.25.32.1
~/.config/opencode $ nc -vz $(ip route show default | awk '{print $3}') 37645
(it's freeze here. Used Ctrl+C)
^C
~/.config/opencode $ wsl.exe --version
Версия WSL: 2.6.3.0
Версия ядра: 6.6.87.2-1
Версия WSLg: 1.0.71
Версия MSRDC: 1.2.6353
Версия Direct3D: 1.611.1-81528511
Версия DXCore: 10.0.26100.1-240331-1435.ge-release
Версия Windows: 10.0.19045.7058
```

Here from PS
```log
Get-NetTCPConnection -LocalPort 37645 -State Listen | Format-List LocalAddress,LocalPort,OwningProcess
...

Thanks for testing and for the screenshots/logs. The desktop side looks like it started TCP IPC correctly and wrote the discovery file, so I want to confirm whether this is WSL networking before changing anything.

Could you run these and paste the output?

In WSL:

```bash
cat /mnt/c/Users//AppData/Roaming/OpenPets/runtime/ipc.json
nc -vz 127.0.0.1 37645
ip route show default | awk '{print $3}'
nc -vz $(ip route show default | awk '{print $3}') 37645
wsl.exe --version
```

In Windows PowerShell:

```powershell
Get-NetTCPConnection -LocalPort 37645 -State Listen | Format-List LocalAddress,LocalPort,OwningProcess
Test-NetConnection -ComputerName 127.0.0.1 -Port 37645
wsl --status
```

Please replace `37645` with the current port from your `ipc.json` if it changes after restarting OpenPets.

My current suspicion is that WSL can read the discovery file, but `127.0.0.1` from WSL is not reaching Windows localhost in your WSL networking mode. These commands should confirm that b...

```log
2026-05-14T20:59:01.407Z INFO app logger initialized logFile="C:\\Users\\***\\AppData\\Roaming\\@open-pets\\desktop\\logs\\openpets.log" previousLogFile="C:\\Users\\***\\AppData\\Roaming\\@open-pets\\desktop\\logs\\openpets.previous.log" level="debug" console=false
2026-05-14T20:59:01.409Z INFO app startup begin version="2.0.7" platform="win32" arch="x64" packaged=true pid=5308
2026-05-14T20:59:01.462Z INFO ipc server started endpointKind="tcp" endpoint="tcp://127.0.0.1:37645" discoveryPath="C:\\Users\\***\\AppData\\Roaming\\OpenPets\\runtime\\ipc.json"
2026-05-14T20:59:01.439Z INFO tray created
2026-05-14T20:59:01.488Z INFO pet.window default window create windowId=1 position=...

Fixed in `958f842` and released in `v2.0.5`.

This adds an opt-in loopback TCP IPC transport for WSL/Windows setups. Same-OS installs still use the default named pipe/Unix socket transport, but WSL clients can now connect to the Windows desktop app with:

```sh
OPENPETS_IPC_ENDPOINT=tcp://127.0.0.1:
```

Docs: `docs/wsl-ipc.md`