VS Code extension: add an option to open external links in VS Code's integrated browser

Open 💬 2 comments Opened Apr 17, 2026 by frznn

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

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗