[Bug][Windows] Service wrapper fails to restart when bun.exe is killed by external process (VPN/TUN driver) #5913

Client or integration

Other

Area

Dashboard

Summary

When bun.exe (the opencodex proxy process) is killed by an external process—such as a VPN or Clash for Windows TUN driver loading during network stack reset—the Windows service wrapper (opencodex-service.cmd) fails to restart it. The batch wrapper only restarts on ERRORLEVEL NEQ 0, but TerminateProcess by an external killer often results in ERRORLEVEL=0 or an undefined value. The wrapper therefore treats the kill as a clean exit, terminates normally, and Task Scheduler records success—so RestartOnFailure never triggers.
Expected: The service should detect that bun.exe died (regardless of exit code) and automatically restart it, so the proxy recovers without manual intervention.
Actual: The proxy stays dead until the user manually runs ocx stop && ocx start.

Reproduction

Reproduction

1. Install and start the service:
   ocx service install
   ocx start
2. Verify proxy is healthy:
   curl http://localhost:10100/healthz
   :: returns 200
3. Open Clash for Windows (or any VPN with TUN/network-filter driver). The problem occurs as soon as the software initializes its network stack—no login or connection required.
4. Within seconds, observe that the proxy is dead:
   curl -v http://localhost:10100/healthz
   :: Connection refused on both ::1 and 127.0.0.1

netstat -ano | findstr 10100
:: (empty — no listener)

ocx status
:: Proxy: not running
5. Check service log — confirms unclean shutdown:
C:\Users\yx.opencodex\service.log
:: Shows: "Previous session (PID xxxxx) did not shut down cleanly"
6. Exiting Clash/VPN does not restore the proxy. Only manual restart works:
ocx stop
ocx start
Frequency: Reproducible every time. Occurs consistently whenever Clash for Windows or 零信任VPN (Sangfor aTrust/EasyConnect) is opened, even without logging in.

Version

2.59.0

Operating system

Windows 11 (Chinese locale), 64-bit

Provider and model

No response

Logs or error output

Screenshots and supporting files

No response

Redacted configuration

Checks

• I searched existing issues and documentation.
• I removed secrets, tokens, account details, request credentials, and personal data.