Cursor 3.0 on Windows: Codex file links open external browser instead of IDE with open-in-target not supported in extension

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I click file links generated by Codex in chat, Cursor does not open the file inside the editor.
Instead, it launches the external browser to a URL like:

https://file+.vscode-resource.vscode-cdn.net/c%3A/Users/mrmei/.cursor/extensions/openai.chatgpt-26.5401.11717-win32-x64/webview/
The browser then fails with DNS / site not reachable.

Relevant log from Codex:

open-in-target not supported in extension
url=vscode://codex/open-in-targets
Log path:

C:\Users\mrmei\AppData\Roaming\Cursor\logs\20260403T095629\window1\exthost\openai.chatgpt\Codex.log
I already tried clearing Cursor caches, deleting and reinstalling the Codex extension, and restarting Cursor. The issue still reproduces.

Steps to Reproduce

Open Cursor on Windows in a local workspace.
Use Codex chat and let it create or reference a local file.
Click the file link shown in chat.
Observe that Cursor opens the external browser instead of opening the file in the editor.

Expected Behavior

Clicking a Codex-generated local file link should open the target file directly inside Cursor editor, not in the external browser.

Operating System

Windows 10/11

Version Information

Cursor: 3.0.6
VS Code engine: 1.105.1
Codex extension: openai.chatgpt-26.5401.11717-win32-x64
User profile path: C:\Users\mrmei

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report.

We looked into it. This is an issue in the OpenAI Codex extension, not Cursor. Here’s why:

  1. The message open-in-target not supported in extension with the URL vscode://codex/open-in-targets is generated by the Codex extension itself. Cursor doesn’t have anything like that in its code.

  2. The extension uses the vscode://codex/ protocol scheme, which is VS Code specific. Cursor uses its own cursor:// protocol, and the Codex extension isn’t adapted for it.

  3. The file+.vscode-resource.vscode-cdn.net URL is an internal webview URI. The extension incorrectly sends it to the external browser as a fallback when open-in-target fails.

I’d recommend reporting this to the OpenAI Codex extension developers. They need to add cursor:// protocol support to work correctly in Cursor.

As a workaround, you can manually open the file via Ctrl+P Quick Open using the filename shown in the Codex chat.

Let me know if you have any other questions.