Codex agent exits and MOI reports inconsistent server state

Summary

The Codex agent connection exits immediately in a newly initialized MOI workspace. The Agent page shows:

codex app-server exited

The workspace UI remains available, but messages cannot be sent.

Environment

• macOS
• MOI CLI: 0.10.0
• MOI workspace skill: 0.13.0
• Codex CLI: 0.144.6
• Bun: 1.4.0
• Harness: Codex

Steps to reproduce

1. Initialize the project with moi init --harness=codex.
2. Run moi skill update.
3. Start MOI and open the generated workspace URL.
4. Open the Agent tab.
5. Observe the login prompt and the red codex app-server exited error.

Actual behavior

• The Agent page displays codex app-server exited.
• The message field is disabled, so the agent cannot be used.
• Running moi start reports:

  Server is already running on http://localhost:13337
  

• At the same time, moi status reports:

  Server is not running
  cli version 0.10.0
  

• A Bun process is listening on both MOI ports 13337 and 13059.

Expected behavior

MOI should connect to the Codex app-server and allow messages to be sent. The CLI should also report a consistent server state.

A screenshot showing the Agent error is available and will be attached in a follow-up comment.

Reproduce the failure with moi init --harness=codex, moi skill update, moi start, and moi status, then inspect the Agent tab and the CLI's server-state reporting entry points. Compare the Codex app-server connection failure with the Bun process listening on ports 13337 and 13059. Done means the Agent accepts messages and moi start and moi status report a consistent server state.