openai / openai/codex

[VS Code][Linux] Opening a Plan crashes the Plan summary UI in 26.901.22334; downgrade to 26.825.51511 fixes it

Open
#43,285 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug extension plan
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the IDE extension are you using?

Failing: openai.chatgpt 26.901.22334 (linux-x64)

Working after rollback: openai.chatgpt 26.825.51511 (linux-x64)

Which IDE are you using?

Visual Studio Code

What platform is your computer?

Linux x86_64

What issue are you seeing?

Opening a Codex Plan consistently crashes the Plan summary view and replaces it with the generic error screen:

ChatGPT hit a snag
Something went wrong. Try again to continue

The failure is specific to the newer extension build. Downgrading the extension from 26.901.22334 to 26.825.51511 fixes the issue immediately; the same Plan-opening workflow works again without changing the workspace or Codex state.

The extension log shows a React error boundary in the Plan-summary frontend. The stack begins in the Plan-specific assets:

[error] error boundary componentStack="
    at Lt (.../openai.chatgpt-26.901.22334-linux-x64/webview/assets/plan-summary-item-content-47f2ac5413e9.js:1:27047)
    at It (.../openai.chatgpt-26.901.22334-linux-x64/webview/assets/plan-summary-item-content-47f2ac5413e9.js:1:26774)
    at div (<anonymous>)
    at c (.../openai.chatgpt-26.901.22334-linux-x64/webview/assets/plan-summary-page-42f312a55a1d.js:1:600)
    at s (.../openai.chatgpt-26.901.22334-linux-x64/webview/assets/plan-summary-page-42f312a55a1d.js:1:228)
    ...
" name=AppRoutes

Immediately beforehand, the log also shows:

[error] Error fetching httpStatus=403 statusText=Forbidden url=/settings/user

[warning] sa_server_request_failed
attachAuth=false
attachIntegrityState=false
method=get
routePattern=/settings/user
status=403
url=/settings/user

I am not claiming that the /settings/user 403 is the root cause; the visible crash is recorded by the frontend error boundary while rendering plan-summary-item-content / plan-summary-page.

What steps can reproduce the bug?
  1. Install/update the Codex VS Code extension to 26.901.22334 on Linux x64.
  2. Open Codex in VS Code.
  3. Open a Plan.
  4. The Plan view fails and shows ChatGPT hit a snag.
  5. Repeat: the issue occurs consistently.
  6. Downgrade the extension to 26.825.51511.
  7. Reload/restart the VS Code extension host/window as needed.
  8. Open the same Plan workflow again.
  9. The Plan opens normally.
What is the expected behavior?

The Plan summary should render normally in the VS Code Codex webview.

An unrelated settings request failure, if it is unrelated, should not cause the Plan route to fail; and if malformed or unexpected Plan data is responsible, the Plan renderer should fail gracefully rather than taking down the entire route.

Additional information

This appears to be a regression introduced between these two extension versions:

26.825.51511  -> works
26.901.22334  -> Plan summary crashes

The failing stack is inside the Plan-specific frontend chunks (plan-summary-item-content and plan-summary-page), which makes this look more like a Plan renderer regression than a general Codex backend/authentication failure.

Workaround: pin/downgrade to 26.825.51511.

A screenshot of the ChatGPT hit a snag screen and the full sanitized log excerpt are available if useful.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce on Linux x64 with extension 26.901.22334, then compare the working 26.825.51511 behavior. Start with the Plan webview assets named in the log, especially plan-summary-item-content and plan-summary-page, and check the surrounding /settings/user 403 without assuming it is causal. Done means the Plan summary renders normally instead of showing the generic error screen.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, vscode
Domain
devtools, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.