Native Windows app-server daemon/service to enable CLI “proxy” terminal attachment (no WSL)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
CLI
What feature would you like to see?
Summary
Please support running the Codex app-server as a native Windows background daemon/service (no WSL) so a desktop app can connect to an already-running agent/session and open/view it in a terminal tab via the existing remote terminal UI / “proxy” workflow.
Problem / Why
My app needs to take an already-running app-server agent/session and view/control it in a terminal tab. Today this daemon-style workflow is effectively Unix/WSL-oriented; I need an equivalent native Windows option.
Request
A supported way to run codex app-server persistently on Windows (background process and/or Windows Service).
A stable local endpoint clients can attach to (WebSocket listen address/port).
A clear attach/re-attach flow so a terminal tab can connect to an existing session (not spawning a new agent).
Expected behavior / regression
Open agent working in app server in cli without work stopping so I can read / interact. Regression: process ownership, automated work.
Start daemon once; app can detect it and connect. Reaches to the same running session/agent and can reconnect after app restarts.
Localhost-only option for security (and any recommended auth/ACL guidance for Windows).
Environment
Windows version: 11
Codex CLI version: latest 152
Install method: terminal
embedded TUI vs launching external terminal: both
Notes
This is specifically for the “proxy” function that lets the CLI view/control a working app-server agent from the running server.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing app-server proxy and remote-terminal workflow, including how clients attach to sessions and use the WebSocket endpoint. Then investigate the Windows 11 process or service requirements and the existing reconnect behavior. Done means a documented native Windows daemon or service can preserve a running session, allow terminal attachment and re-attachment, and support localhost-only operation with security guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design, cli, operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100