# Cursor 3.0 on Windows: Codex file links open external browser instead of IDE with open-in-target not supported in extension **URL:** \ **Category:** Bug Reports\ **Tags:** windows, extensions\ **Created:** [April 3, 2026, 5:08am UTC](https://forum.cursor.com/t/cursor-3-0-on-windows-codex-file-links-open-external-browser-instead-of-ide-with-open-in-target-not-supported-in-extension/156563 "2026-04-03T05:08:56Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mrmei](https://avatars.discourse-cdn.com/v4/letter/m/d26b3c/32.png) [@mrmei](https://forum.cursor.com/u/mrmei)\ **Post date:** [April 3, 2026, 5:08am UTC](https://forum.cursor.com/t/cursor-3-0-on-windows-codex-file-links-open-external-browser-instead-of-ide-with-open-in-target-not-supported-in-extension/156563/1 "2026-04-03T05:08:56Z")
### 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/](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 ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [April 3, 2026, 6:51am UTC](https://forum.cursor.com/t/cursor-3-0-on-windows-codex-file-links-open-external-browser-instead-of-ide-with-open-in-target-not-supported-in-extension/156563/5 "2026-04-03T06:51:37Z")
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. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [April 25, 2026, 6:52am UTC](https://forum.cursor.com/t/cursor-3-0-on-windows-codex-file-links-open-external-browser-instead-of-ide-with-open-in-target-not-supported-in-extension/156563/6 "2026-04-25T06:52:30Z")
Closed on April 25, 2026, 6:52am UTC This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.