Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix VS Code/Cursor file links in Codex responses do not open targets on macOS [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#17774•Fetched 2026-04-15 06:28:34
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
yyhuniyyhuni
Participants
github-actions[bot]github-actions[bot]yyhuniyyhuni
Timeline (top)
cross-referenced ×2labeled ×2closed ×1commented ×1

Error Message

Error fetching errorMessage="open-in-target not supported in extension" ... url=vscode://codex/open-in-targets 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

Code Example

Error fetching errorMessage="open-in-target not supported in extension" ... url=vscode://codex/open-in-targets

---

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
RAW_BUFFERClick to expand / collapse

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?

  1. Open VS Code or Cursor on macOS.
  2. Install the Codex IDE extension openai.chatgpt 26.409.20454-darwin-arm64.
  3. Start a Codex thread and ask for output that includes clickable file references or code-location links.
  4. Click one of those file/location links in the Codex panel.
  5. 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.

extent analysis

TL;DR

The issue can likely be resolved by updating the Codex IDE extension to a version that supports the "open-in-target" feature or by using a workaround that handles the target-open request.

Guidance

  • Verify that the "open-in-target" feature is supported in the current version of the Codex IDE extension by checking the extension's documentation or release notes.
  • Check if there are any platform-specific limitations or workarounds for the "open-in-target" feature on macOS.
  • Investigate if there are any configuration options in the Codex IDE extension that can be adjusted to enable the "open-in-target" feature.
  • Consider reaching out to the extension developers for further assistance or to report the issue.

Example

No code snippet is provided as the issue is related to the Codex IDE extension and its interaction with the IDE, rather than a specific code problem.

Notes

The issue appears to be platform-dependent, as it is reproducible on macOS but not on Windows. The extension logs indicate that the "open-in-target" feature is not supported in the current version of the extension.

Recommendation

Apply workaround: The user may need to use a temporary workaround, such as manually opening the referenced file and navigating to the target line/column, until an updated version of the Codex IDE extension is released that supports the "open-in-target" feature.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#API middleware#SSR setup#ISR setup#authentication setup#request error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix VS Code/Cursor file links in Codex responses do not open targets on macOS [1 comments, 2 participants]