›_ Codex Issues
Codex Issues / #7487

VS Code (Windows): openai-codex:/… fails to resolve when creating Chat: New OpenAI Codex

Open 💬 5 comments Opened Dec 2, 2025 by Gadansky
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

Summary
Creating a new Codex chat in VS Code fails to open the resource; VS Code reports Unable to resolve resource openai-codex:/<untitled-id>. The custom editor/provider for the openai-codex scheme never resolves.

Environment

  • OS: Windows (WSL installed)
  • VS Code Stable: 1.106.3
  • VS Code Insiders: 1.107.0-insider
  • Extension: openai.chatgpt v0.4.46
  • Workspace: Trusted
  • Launch flags: --enable-proposed-api openai.chatgpt
  • Reproducible with a clean user data dir + extensions dir

Steps to Reproduce (minimal)
1) PowerShell:
``powershell
$env:TEMP_CODEx = "$env:TEMP\vscode-codex-test-insiders"
Remove-Item -Recurse -Force $env:TEMP_CODEx -ErrorAction SilentlyContinue
& "$env:LOCALAPPDATA\Programs\Microsoft VS Code Insiders\bin\code-insiders.cmd" --user-data-dir "$env:TEMP_CODEx\user" --extensions-dir "$env:TEMP_CODEx\exts" --install-extension openai.chatgpt --enable-proposed-api openai.chatgpt
& "$env:LOCALAPPDATA\Programs\Microsoft VS Code Insiders\bin\code-insiders.cmd" --user-data-dir "$env:TEMP_CODEx\user" --extensions-dir "$env:TEMP_CODEx\exts" --enable-proposed-api openai.chatgpt
``
2) In the window, mark the workspace as Trusted.
3) Run “Chat: New OpenAI Codex”.

Actual Result

  • VS Code shows an error and console/renderer log contains:

Unable to resolve resource openai-codex:/<untitled-id>

  • The openai-codex scheme never resolves to the custom editor/panel.

Expected Result

  • The Codex panel/task opens without error.

Notes

  • Same behavior on VS Code Stable 1.106.3 with a clean profile.
  • Setting workbench.editorAssociations with chatgpt.conversationEditor and openai-codex:/**/* does not change the result.
  • No other extensions loaded; workspace is trusted; WSL present; proposed API enabled.

Logs

  • Renderer and exthost logs captured from the clean Insiders profile: renderer.log and exthost.log (can share privately if needed).

View original on GitHub ↗

5 Comments

Gadansky · 8 months ago

Adjunto logs del repro limpio (VS Code Insiders 1.107.0-insider, extensión openai.chatgpt v0.4.46, Windows, workspace trusted, lanzado con --enable-proposed-api openai.chatgpt). Gist con renderer.log y exthost.log: https://gist.github.com/Gadansky/f8e84922cd80ff6c76bb50035c9291aa

etraut-openai contributor · 8 months ago

We haven't seen this failure mode before. I suspect it's specific to your system — perhaps a configuration or corruption issue. Let's see if we can figure it out.

Was this working with previous versions of codex, or is this the first time you've tried to run codex on your system?

Do you have any custom (non-default) configuration settings in your codex.toml file or in your settings.json file in VS Code?

Do you have any environment variables defined that could affect VS Code's ability to resolve the extension?

We have some additional documentation and troubleshooting tips specific for Windows here.

Gadansky · 8 months ago

Thanks for jumping in.

Answers:
1) First time trying Codex on this machine; never had a working version. The error happens on the first run, both Stable 1.106.3 and Insiders 1.107.0-insider.
2) No custom codex.toml (none present). VS Code settings are essentially default; only entries are workbench.colorTheme and the workbench.editorAssociations I added while debugging (chatgpt.conversationEditor for openai-codex:/**/*).
3) No intentional env vars for VS Code/extensions. WSL is installed; otherwise default Windows environment.

Also reproduced with completely clean --user-data-dir/--extensions-dir and --enable-proposed-api openai.chatgpt with a trusted workspace. Logs are attached above.

Happy to try extra logging/diagnostics if helpful.

Gadansky · 8 months ago

Update after clean runs on Windows (VS Code 1.106.3):

1) Clean profile, cleared ELECTRON_*:
code --verbose --log=trace --user-data-dir "%USERPROFILE%\codex-clean-user" --extensions-dir "%USERPROFILE%\codex-clean-exts"

  • When running workbench.action.chat.openNewSessionEditor.openai-codex, renderer.log shows:

Error: Unable to resolve resource openai-codex:/untitled-c5eba9d3-6128-412f-bee9-7b3ebaeaa7d6

  • Codex.log is empty (0 bytes). exthost.log only shows activation on onChatSession:openai-codex.

2) Same with proposed API and clean profile:
code --enable-proposed-api openai.chatgpt --verbose --log=trace --user-data-dir "%USERPROFILE%\codex-proposed-user" --extensions-dir "%USERPROFILE%\codex-proposed-exts"

  • renderer.log shows twice: Error: Unable to resolve resource openai-codex:/untitled-95f573e4-f01f-4d82-a944-6638c2b50304
  • Codex.log again 0 bytes; exthost.log clean besides activation.

Net: Codex backend never starts; the openai-codex resource handler fails immediately even with proposed API and clean state.

codex-clean-logs-20251202T172949.zip
codex-proposed-logs-20251202T173422.zip

al6x · 6 months ago

I have same problem. Codex works in sidebar, but when I try to create new large chat window it fails, with log

Error: Unable to resolve resource openai-codex:/untitled-xxxxx-xxxx....