[Bug] VS Code / Desktop login fails: no listener on localhost:1455 (CLI works)
What version of the Codex App are you using (From “About Codex” dialog)?
26.409.7971.0
What subscription do you have?
Plus
What platform is your computer?
MINGW64_NT-10.0-19045 3.6.5-22c95533.x86_64 x86_64
What issue are you seeing?
Codex CLI login works correctly, but Codex Desktop and VS Code extension fail to complete login.
The failure appears to be caused by the local OAuth callback server not starting (no process listening on localhost:1455).
What steps can reproduce the bug?
- Open Codex (Desktop app or VS Code extension)
- Click "Continue With ChatGPT"
- Browser opens for authentication
- Complete login successfully in browser
- Browser attempts to redirect to:
http://localhost:1455/auth/callback
What is the expected behavior?
- Codex should start a local server on 127.0.0.1:1455
- Browser callback should be received successfully
- Login should complete and session should be established
Additional information
Actual Behavior
- Immediately after clicking "Continue With ChatGPT", the following error appears:
````
Sign-in failed: Login server error: Login was not completed
- The browser eventually redirects to
http://localhost:1455/...but shows:
- "This site can’t be reached" / connection refused
- At the time of failure, running:
``powershell``
netstat -ano | findstr :1455
shows no LISTENING process on port 1455
---
Important Comparison (CLI vs Extension)
- When running CLI login:
``bash``
codex login
then:
``powershell``
netstat -ano | findstr :1455
shows:
````
TCP 127.0.0.1:1455 LISTENING
→ Login completes successfully
- When using Desktop app or VS Code extension:
- No LISTENING on 1455
- Login fails immediately
---
Key Observation
This strongly suggests:
The Codex Desktop / VS Code extension fails to start the local OAuth callback server on localhost:1455, causing the login flow to fail before completion.
---
Additional Checks Performed
- Not using WSL / Remote environments
- No firewall or proxy blocking localhost
- Port 1455 is not occupied by other processes
- CLI login works reliably on same machine
- Issue reproducible every time in Desktop app and VS Code extension
---
Possible Root Cause
- Local login server (OAuth callback listener) not starting in Desktop / extension
- Port binding failure not surfaced properly
- Missing fallback (e.g. device code flow) in extension
---
Impact
- Unable to use Codex Desktop or VS Code extension with ChatGPT login
- CLI is the only working interface
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗