Mac Codex Remote remote fail — WebSocket HTTP 503
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Environment:
macOS 26.6.2, Apple Silicon
Desktop app 26.903.61454
App-bundled CLI 0.153.4 / standalone 0.154.0
Symptoms:
The Mac appears offline on mobile.
Enabling remote control on the Mac produces the error “Unable to update remote control availability.”
The error “Make sure only one ChatGPT instance is running” also occurs.
Steps tried:
Restarted the app; the issue occurs on both Wi-Fi and a mobile hotspot.
After installing the standalone version, confirmed that the persistent server was running normally, but the connection still failed.
Stopping the additional server and retrying in the app produced the same result.
Observed remote control logs:
2026-09-10 15:06:06 KST
HTTP 503 Service Unavailable
upstream connect error or disconnect/reset before headers.
reset reason: connection termination
CF-Ray: a38c3eb61d09d1da-ICN
Please investigate the remote connection service and relay path.
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 reproducing remote control on macOS while collecting the remote connection logs, focusing on the WebSocket HTTP 503 and upstream reset. Trace the relay path and the interaction between the desktop app and standalone persistent server. Done means the Mac appears online on mobile and remote control availability updates without the duplicate-instance error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop-dev, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100