Codex remote control cannot start on Windows, CLI reports daemon lifecycle is Unix-only

Open 💬 2 comments Opened Jun 27, 2026 by hiwuhuazhang-ops

What version of the Codex App are you using (From “About Codex” dialog)?

版本 26.623.42026 • 发布于 2026年6月27日

What subscription do you have?

Codex remote control cannot start on Windows, CLI reports daemon lifecycle is Unix-only

What platform is your computer?

_No response_

What issue are you seeing?

I cannot enable Codex remote control on Windows even after reinstalling Codex Desktop and confirming ChatGPT login is valid.

Environment:

  • OS: Windows
  • Codex Desktop: OpenAI.Codex_26.623.5546.0_x64
  • Codex CLI: codex-cli 0.142.3
  • Login status: Logged in using ChatGPT
  • Config includes:

[features]
remote_connections = true
remote_control = true

Desktop symptom:

  • The Codex Desktop UI shows:

"Could not enable remote control. Please ensure only one instance of Codex is running."

CLI reproduction:

  1. Run:

codex remote-control start --json

  1. Actual result:

Error: codex app-server daemon lifecycle is only supported on Unix platforms

  1. Run:

codex app-server daemon enable-remote-control

  1. Actual result:

Error: codex app-server daemon lifecycle is only supported on Unix platforms

Expected:

  • Codex remote control should start or the Windows desktop app should provide a supported Windows path for enabling remote control.

Notes:

  • I have already reinstalled Codex Desktop.
  • I verified the CLI is installed and authenticated.
  • The issue persists after adding remote_connections=true and remote_control=true to config.toml.

What steps can reproduce the bug?

Feedback ID: 019f09b2-12c9-74e0-b195-3f1ec941592d

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗