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

Open 💬 5 comments Opened Dec 2, 2025 by Gadansky

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 ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗