VS Code/Cursor file links in Codex responses do not open targets on macOS
Resolved 💬 1 comment Opened Apr 14, 2026 by yyhuni Closed Apr 14, 2026
What version of Codex is running?
Codex IDE extension openai.chatgpt 26.409.20454-darwin-arm64
Which model were you using?
Not model-specific. This happens when clicking file/location links rendered in Codex responses.
What platform is your computer?
macOS 26.4.1 (arm64)
Additional host versions:
- VS Code 1.115.0
- Cursor 3.1.10
What steps can reproduce the bug?
- Open VS Code or Cursor on macOS.
- Install the Codex IDE extension
openai.chatgpt 26.409.20454-darwin-arm64. - Start a Codex thread and ask for output that includes clickable file references or code-location links.
- Click one of those file/location links in the Codex panel.
- Observe that nothing opens in the IDE.
This reproduces in both VS Code and Cursor on the same machine.
What is the expected behavior?
The clicked file/location link should open the referenced file in the current IDE and reveal the target line/column.
What do you see instead?
Nothing opens.
The extension logs repeated errors indicating the target-open request is not handled:
Error fetching errorMessage="open-in-target not supported in extension" ... url=vscode://codex/open-in-targets
Additional information
I observed this on 2026-04-14.
Relevant local logs:
- Cursor:
/Users/yangyang/Library/Application Support/Cursor/logs/20260414T162645/window1/exthost/openai.chatgpt/Codex.3.log- Example timestamp:
2026-04-14 16:55:01.598 - VS Code:
/Users/yangyang/Library/Application Support/Code/logs/20260414T151125/window1/exthost/openai.chatgpt/Codex.6.log- Example timestamps:
2026-04-14 17:00:42.596,2026-04-14 17:05:11.393
Representative log excerpt:
2026-04-14 16:55:01.598 [error] Error fetching errorMessage="open-in-target not supported in extension" errorName=Error ... url=vscode://codex/open-in-targets
Notes:
- I reproduced this in both VS Code and Cursor with the same extension version on the same Mac, so it does not appear to be Cursor-only.
- A Windows user I compared against did not reproduce, so this may be platform-dependent or host-dependent.
- I can provide a screen recording if useful.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗