VS Code extension opens file+.vscode-resource.vscode-cdn.net links in external browser
Resolved 💬 8 comments Opened Feb 26, 2026 by htazq Closed Feb 26, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
Summary
Clicking certain file/reference links in the Codex VS Code extension opens the system browser with a URL like:
https://file+.vscode-resource.vscode-cdn.net/c%3A/Users/.../.vscode/extensions/openai.chatgpt-0.4.76-win32-x64/webview/...
The browser then fails with ERR_CONNECTION_CLOSED.
These links appear to be VS Code webview resource URLs and should not be handled as external web links.
Environment
- Extension:
openai.chatgpt0.4.76(win32-x64) - OS: Windows
- VS Code: (can provide exact build if needed)
Actual behavior
- Clicking a Codex-rendered reference/file link triggers external browser navigation.
- External URL starts with
https://file+.vscode-resource.vscode-cdn.net/... - Browser shows
ERR_CONNECTION_CLOSED.
Expected behavior
- Link should open inside VS Code (file in workspace + line navigation), or be rendered as non-clickable webview-internal resource.
- It should not call external browser for
file+.vscode-resource...URLs.
Repro steps (minimal)
- In Codex panel, generate a response containing a clickable file/reference link.
- Click the link.
- Observe that VS Code opens default browser to
file+.vscode-resource.vscode-cdn.netURL. - Browser fails with
ERR_CONNECTION_CLOSED.
Notes
- This seems related to link handling/routing (internal IDE resource vs external URI).
- Related (not same symptom): #12661 (file links opening in browser).
8 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Additional details for triage:
https://file+.vscode-resource.vscode-cdn.net/c%3A/Users/<redacted>/.vscode/extensions/openai.chatgpt-0.4.76-win32-x64/webview/...
If useful, I can also provide renderer/exthost logs from VS Code Developer Tools.
here is the same issue as well.
Facing the same issue.
Facing the same issue.
have been pinging OpenAI devs on X for weeks regarding this issue.. Sometimes, sporadically it gets fixed (the file opens, sometimes even with the specific line focused), but it is very inconsistent. I can't believe they can't make it to work properly. The raw LLM output is usually something like
[file.py](d:/Dev/file.py#L68)but the extension consistently fails to render it properly.
Facing the same issue.
Still the same issue.