codex - 💡(How to fix) Fix VS Code extension keeps switching from ChatGPT Plus auth to API key / Codex mode [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17207Fetched 2026-04-10 03:43:57
View on GitHub
Comments
3
Participants
3
Timeline
6
Reactions
0
Timeline (top)
commented ×3labeled ×3

Root Cause

This makes the extension unreliable because the auth state is not sticky and the extension does not preserve the subscription-backed session between launches or during normal use.

RAW_BUFFERClick to expand / collapse

Problem

For the last 2-3 days, the VS Code Codex extension has started forgetting my ChatGPT Plus subscription state and switching me to API-key/Codex auth. It then repeatedly asks me to relogin before it will use the ChatGPT Plus subscription again.

What I expected

  • Stay on my ChatGPT Plus subscription session
  • Keep using subscription-backed auth unless I explicitly switch providers
  • Not require constant relogin to get back to the subscription mode

What actually happens

  • Extension silently flips to API key / Codex mode
  • It forgets the ChatGPT Plus subscription state
  • I have to relogin over and over to return to using the subscription

Environment

  • VS Code Codex extension
  • ChatGPT Plus subscription
  • Started happening recently, around the last 2-3 days

Impact

This makes the extension unreliable because the auth state is not sticky and the extension does not preserve the subscription-backed session between launches or during normal use.

Notes

This is different from a simple 401 or one-off login failure. The issue is that the extension keeps reverting away from my ChatGPT Plus session and into API-key/Codex behavior without me asking for that.

extent analysis

TL;DR

The VS Code Codex extension may need a configuration update or a reset to maintain the ChatGPT Plus subscription state and prevent it from switching to API-key/Codex auth.

Guidance

  • Check the extension's settings to ensure that the ChatGPT Plus subscription is properly configured and selected as the default authentication method.
  • Try resetting the extension's authentication cache or storage to see if it resolves the issue with the subscription state not being preserved.
  • Verify that the ChatGPT Plus subscription is active and valid, as an expired or inactive subscription could cause authentication issues.
  • If the issue persists, consider reinstalling the VS Code Codex extension to ensure that all settings and configurations are reset to their defaults.

Notes

The cause of the issue is unclear, but it may be related to a recent update or change in the extension or the ChatGPT Plus service. Further investigation or support from the extension developers may be necessary to fully resolve the issue.

Recommendation

Apply workaround: Try resetting the extension's authentication cache or storage, and verify that the ChatGPT Plus subscription is active and valid, as this may resolve the issue without requiring a full reinstall of the extension.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix VS Code extension keeps switching from ChatGPT Plus auth to API key / Codex mode [3 comments, 3 participants]