Add a --proxy flag to the app-server launch parameters

Resolved 💬 2 comments Opened Mar 23, 2026 by PanicIsReal Closed May 10, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

Codex App-Server

What feature would you like to see?

If we could add a --proxy flag or --forward or something to the app-server so you can forward the app server connection elsewhere would be hugely beneficial to SWE's trying to create an enhanced UI to end users.

Use case:

Having a cloud based service that provides a much more enhanced superset of features by acting as a middleman between the user and the app-server, the only problem is currently to do so users must always download some sort of tunnel/vpn/software middleman etc. to be able to connect their app server to a middleman that can enhance features, provide pagination on results or whatever else. app-server -> middleman transforms data or provides additional features above and beyond -> Data sent to front end device

with a proxy flag the barrier for this would be much less if you could say have your middleman expose an ip/port socket, and then launch codex app-server --proxy ws://cloudprovider:4545 then your middleman cloud only has to worry about interacting with its locally hosted socket. This eliminates users having to download or setup vpns etc.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 5 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #14887

Powered by Codex Action

etraut-openai contributor · 3 months ago

This feature request hasn't received enough upvotes, so I'm going to close it.