Unable to Sign In to Codex VS Code Extension on VS Code Server
What version of Codex is running?
0.4.43
What subscription do you have?
Plus
Which model were you using?
_No response_
What platform is your computer?
Android tablet (Chrome browser)
What issue are you seeing?
When using the Codex VS Code extension on VS Code Server (browser-based VS Code), the login process fails when signing in with a ChatGPT Plus account. The extension does not accept ChatGPT Plus credentials and never completes authentication.
Environment
Platform: VS Code Server / code-server (browser version)
Device: Android tablet (Chrome browser)
Codex Extension Version: latest available
Authentication Method: ChatGPT Plus login (OAuth via OpenAI)
Network: Public HTTPS URL, no VPN/proxy
What steps can reproduce the bug?
- Open VS Code Server in a mobile browser.
- Install and open the Codex extension.
- Choose “Sign in with ChatGPT” or “Sign in with Google/OpenAI account.”
- Attempt to authenticate with a valid ChatGPT Plus subscription.
- Observe that the login fails or stalls, and the extension does not become authenticated.
What is the expected behavior?
Codex extension should allow users with ChatGPT Plus to authenticate successfully or clearly indicate that ChatGPT Plus logins are not supported.
Actual Result
Authentication does not complete.
The extension remains unauthenticated with no clear error message.
On API-key mode, using the same account results in “Quota exceeded”, even though the user has ChatGPT Plus.
Impact
Users with a valid ChatGPT Plus subscription cannot use the Codex extension on VS Code Server, leaving them unable to access coding assistance unless they separately create and fund a Developer API account.
Additional information
ChatGPT Plus does not provide API credits, but this is not clearly communicated in the UI.
The login flow may also be affected by OAuth redirect limitations in browser-based VS Code Server on mobile devices.
A clearer error message or guidance would help prevent user confusion.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗