MrWynn / codex-proxy-launcher

What is codex-proxy-launcher?

codex-proxy-launcher is a small PowerShell utility that launches Codex Desktop with the right proxy environment variables baked into the process. If you've ever dealt with Codex refusing to route WebSocket traffic through your system proxy, this solves that by injecting HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY directly into Codex's process space. It ships as two simple scripts—one for macOS and one for Windows—with CLI commands for start, stop, restart, status, and log viewing. The defaults point to a typical Clash setup on localhost port 7890, but you can override everything with environment variables.

Why is it gaining traction?

The hook here is narrow but real: Codex Desktop's WebSocket connections sometimes ignore the OS-level proxy, which breaks the app for developers behind corporate or regional firewalls. This tool forces both HTTP and WebSocket traffic through your local proxy without needing TUN mode, which is faster and avoids potential routing conflicts. It's a one-trick solution that does exactly that one trick well, with sensible defaults and clear documentation for both platforms.

Who should use this?

This is for developers running Codex Desktop behind a proxy—whether that's corporate restrictions, region-locked APIs, or a Clash/V2Ray setup. If you've been troubleshooting why Codex connects but can't reach certain services, and you've already confirmed your proxy works for everything else, this is your fix. Windows Store/Appx users get special handling since direct execution from WindowsApps is blocked.

Verdict

Use it if you need it. The project is minimal and focused—14 stars reflects its niche audience. Documentation is solid and bilingual, but there's no CI, tests, or release artifacts to speak of. At 0.899% credibility, it's a personal utility that happens to be public, not a community-backed project. If you understand the problem it solves, the risk is essentially zero.