Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix VS Code extension: add an option to open external links in VS Code's integrated browser [1 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#18374•Fetched 2026-04-18 05:55:04
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
frznnfrznn
Participants
frznnfrznn
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

What feature would you like to see?

Please add a VS Code extension setting that lets Codex open external http/https links in VS Code's integrated browser instead of always using the system browser.

Why

When I click documentation, help, or reference links from the Codex sidebar/chat UI, the extension currently sends them through VS Code's external-link path. That pushes me out to the system browser and breaks the in-editor workflow.

VS Code already has an integrated browser, so I would like an extension preference to keep this navigation inside the editor when possible.

This would help with:

  • following documentation links while coding
  • staying in a single-window workflow
  • reducing context switching from the Codex UI

Current behavior

From local inspection of the installed extension:

  • the extension currently opens links via vscode.env.openExternal(...)
  • I do not see a contributed setting in the extension for choosing integrated browser vs system browser

What I'd expect

A Codex setting such as:

  • systemBrowser (current behavior)
  • integratedBrowser

If this depends on additional VS Code platform support, it would still help to:

  • track that dependency here
  • document the current limitation clearly
  • expose the option once VS Code supports it cleanly

Additional information

Environment:

  • VS Code: 1.116.0
  • Codex VS Code extension: 26.415.20818

I searched for similar issues before filing. I found adjacent reports about consent prompts and local/file links opening in the browser, but not this specific request for an integrated-browser preference for external links:

  • #12561
  • #12661
  • #16520

extent analysis

TL;DR

To address the issue, consider adding a new setting to the Codex VS Code extension that allows users to choose between opening external links in the system browser or VS Code's integrated browser.

Guidance

  • Investigate the vscode.env.openExternal function to determine if it can be modified to use the integrated browser instead of the system browser.
  • Check the VS Code API documentation to see if there is a built-in function for opening links in the integrated browser.
  • Consider adding a new setting to the Codex extension, such as linkTarget, with options for systemBrowser and integratedBrowser.
  • Review the existing issues (#12561, #12661, #16520) to ensure that the proposed solution does not introduce any unintended consequences.

Example

// potential example of how the new setting could be implemented
const linkTarget = vscode.workspace.getConfiguration('codex').get('linkTarget');
if (linkTarget === 'integratedBrowser') {
  // use VS Code's integrated browser to open the link
} else {
  vscode.env.openExternal(link);
}

Notes

The implementation of this feature may depend on the availability of a VS Code API for opening links in the integrated browser. If such an API does not exist, it may be necessary to track the dependency and document the current limitation.

Recommendation

Apply workaround: add a new setting to the Codex extension that allows users to choose between opening external links in the system browser or VS Code's integrated browser, and use the integrated browser if possible. This will improve the user experience by reducing context switching and keeping the workflow within the editor.

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#ssr#installation#tensor shape#autograd 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