2 people reported

All time, since Oct 13.

Webview fails in Remote WSL

“The problem prevents developers working in WSL from accessing the Codex panel, even though the Codex backend initializes successfully.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/12575/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Codex webview fails to load in VS Code Remote WSL. After a VS Code update, webview assets return HTTP 401 for WSL distributions with uppercase letters like Ubuntu.

Is this your bug?

File my report
Where
VS Code extension
Error text
Codex could not start — The extension could not start its user interface.
Versions
26.1007.21434
Platforms
Windows
How bad
Breaks a normal workflow.

Part of: Codex VS Code extension shows "Codex could not start" and its sidebar UI never loads9 bugs

  1. Sidebar renderer_ready_timeout52 people
  2. Sidebar renderer_ready_timeout18 people
  3. Sidebar UI fails to start4 people
  4. Extension UI fails to start128 people
  5. User interface fails to start23 people
  6. Sidebar UI fails to start3 people
  7. Extension UI fails to start2 people
  8. Codex UI fails to start6 people

Original reports2, newest first

  1. Codex Extension (Webview) Fails After VS Code Update on WSL — WorkaroundOn the forum#1406245
  2. Codex WebView assets return HTTP 401 in VS Code Remote WSL after VS Code 1.141.1 updateOn GitHub#53840

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.