VS Code extension authentication fails after update (attachAuth=false, GET /settings/user returns 403)

[wyltonmendes100-cpu]

What version of the IDE extension are you using?

openai.chatgpt-26.5721.30844-win32-x64

What subscription do you have?

openai.chatgpt-26.5721.30844-win32-x64

Which IDE are you using?

Visual Studio Code 1.130.0

What platform is your computer?

Windows 11 x64

What issue are you seeing?

The ChatGPT VS Code extension fails to authenticate.

The sidebar only displays:

Oops, something went wrong

The ChatGPT website, Codex website and platform.openai.com all work correctly with the same account.

Environment:

• VS Code 1.130.0
• Windows 11 x64
• Extension: openai.chatgpt-26.5721.30844-win32-x64
• Login: Google
• Subscription: ChatGPT Pro

Output log:

routePattern=/settings/user
status=403
attachAuth=false
attachIntegrityState=false

Additional observations:

• ChatGPT Web works correctly.
• Codex Web works correctly.
• Platform works correctly.
• The account is authenticated.
• Reinstalling the extension did not help.
• Tested both Release and Pre-Release.
• VS Code is fully updated.
• The extension does not expose any Sign In or Sign Out command.
• The request to /settings/user is sent with attachAuth=false, which results in HTTP 403.

The issue started suddenly after previously working normally.

The extension was working until approximately 01:00 (local time). Around 07:00 on the same day it started consistently showing "Oops, something went wrong" without any local configuration changes.

If needed, I can provide:

• VS Code Output logs
• Developer Tools logs
• Network logs
• Screenshots

What steps can reproduce the bug?

1. Install the ChatGPT VS Code extension (openai.chatgpt-26.5721.30844-win32-x64).

2. Sign in using a Google account with an active ChatGPT Pro subscription.

3. Open the ChatGPT sidebar.

4. Open the Codex panel.

5. The panel immediately displays:

Oops, something went wrong

6. Open View → Output → Codex.

7. The following log appears:

routePattern=/settings/user
status=403
attachAuth=false
attachIntegrityState=false

The issue happens consistently on every VS Code restart.

What is the expected behavior?

The ChatGPT/Codex extension should authenticate successfully and display the normal Codex interface without any authentication errors.

Additional information

Additional information:

• ChatGPT Web works correctly.

• Codex Web works correctly.

• platform.openai.com works correctly.

• Login is performed with Google.

• Subscription is ChatGPT Pro.

• The issue started suddenly after previously working normally.

• Reinstalling the extension did not help.

• Tested both Release and Pre-Release versions.

• VS Code is fully updated.

• The extension does not expose any Sign In or Sign Out command.

• Output log consistently shows:
  routePattern=/settings/user
  status=403
  attachAuth=false
  attachIntegrityState=false

• The extension attempts to access /settings/user without attaching authentication.

[alitchmore]

Experiencing this same issue

[wyltonmendes100-cpu]

This appears related to #35182. In my case, the Codex Output log also consistently shows:

routePattern=/settings/user
status=403
attachAuth=false
attachIntegrityState=false

ChatGPT Web and Codex Web work normally with the same ChatGPT Pro account.

[qyloxe]

Another Windows user confirms the same failure pattern:

• Codex panel only shows “Something went wrong / try again”
• chatgpt-account-lookup reports authenticatedAccountPresent=true
• the next request fails with 403 Forbidden for /settings/user
• the webview then enters an error boundary
• reinstalling the extension, reloading/restarting VS Code, and signing out in the browser did not help

Affected version: v26.721.30844.

Downgrading specifically to v26.715.61943 immediately restored normal operation. This strongly suggests a regression introduced in v26.721.30844 or its associated auth request path rather than missing Codex account permissions or damaged local session data.

[wyltonmendes100-cpu]

Thank you for sharing this!

Your comment helped me identify the root cause. I downgraded from v26.721.30844 to v26.715.61943, restarted the extension, and the issue was resolved immediately.

This confirms that the problem is very likely a regression introduced in v26.721.30844 rather than an account or local configuration issue.

I really appreciate you taking the time to post the workaround—it saved me a lot of troubleshooting.

Thanks!

[alitchmore]

Another Windows user confirms the same failure pattern:

• Codex panel only shows “Something went wrong / try again”
• chatgpt-account-lookup reports authenticatedAccountPresent=true
• the next request fails with 403 Forbidden for /settings/user
• the webview then enters an error boundary
• reinstalling the extension, reloading/restarting VS Code, and signing out in the browser did not help

Affected version: v26.721.30844.

Downgrading specifically to v26.715.61943 immediately restored normal operation. This strongly suggests a regression introduced in v26.721.30844 or its associated auth request path rather than missing Codex account permissions or damaged local session data.

Thanks... this fixed the issue

[diegorost]

Another Windows user confirms the same failure pattern:

• Codex panel only shows “Something went wrong / try again”
• chatgpt-account-lookup reports authenticatedAccountPresent=true
• the next request fails with 403 Forbidden for /settings/user
• the webview then enters an error boundary
• reinstalling the extension, reloading/restarting VS Code, and signing out in the browser did not help

Affected version: v26.721.30844.

Downgrading specifically to v26.715.61943 immediately restored normal operation. This strongly suggests a regression introduced in v26.721.30844 or its associated auth request path rather than missing Codex account permissions or damaged local session data.

It did not help downgrading to that version, still same error

2026-07-25 21:02:06.225 [error] Error fetching httpStatus=403 requestId=a20f7a19ea8bd597-SCL statusText=Forbidden url=/settings/user
2026-07-25 21:02:06.332 [warning] sa_server_request_failed attachAuth=false attachIntegrityState=false error={} hasRequestBody=false method=get requestHeaderNames=["OAI-Language","User-Agent","oai-did","originator","sec-ch-ua","sec-ch-ua-mobile","sec-ch-ua-platform"] routePattern=/settings/user status=403 url=/settings/user
2026-07-25 21:02:06.595 [warning] [git] git.command.complete aborted=false allowedNonZeroExitCodes=null argsCount=3 command="git -c core.hooksPath=NUL -c core.fsmonitor= config --get remote.origin.url" commandArgs=["git","-c","core.hooksPath=NUL","-c","core.fsmonitor=","config","--get","remote.origin.url"] cwd=C:\Users\diego\OneDrive\Developments\private.git durationMs=58 exitCode=1 failureReason=command_failed hostId=local id=7202ab55 isRemote=false outputLimitExceeded=false outputLimitMaxBytes=null outputLimitStream=null requestKind=git-origins source=sidebar_workspace_groups startTimeMs=1785027726536 stderrBytes=0 stdoutBytes=0 subcommand=config success=false timedOut=false
2026-07-25 21:02:14.152 [error] Error fetching httpStatus=403 requestId=a20f7a4b7bcde7ab-SCL statusText=Forbidden url=/settings/user
2026-07-25 21:02:14.153 [warning] sa_server_request_failed attachAuth=false attachIntegrityState=false error={} hasRequestBody=false method=get requestHeaderNames=["OAI-Language","User-Agent","oai-did","originator","sec-ch-ua","sec-ch-ua-mobile","sec-ch-ua-platform"] routePattern=/settings/user status=403 url=/settings/user

2026-07-25 21:02:14.153 [warning] sa_server_request_failed attachAuth=false attachIntegrityState=false error={} hasRequestBody=false method=get requestHeaderNames=["OAI-Language","User-Agent","oai-did","originator","sec-ch-ua","sec-ch-ua-mobile","sec-ch-ua-platform"] routePattern=/settings/user status=403 url=/settings/user