ChatGPT macOS app routes generic URLs to Chrome despite in-app browser configuration

What version of the Codex App are you using (From “About Codex” dialog)?

ChatGPT 26.825.41651 (build 7345)

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Darwin 25.5.0 arm64 arm (macOS 26.5.2, build 25F84)

What issue are you seeing?

Summary

The application involved is the macOS app branded ChatGPT. Its About dialog identifies it as “Powered by Codex & OWL,” version 26.825.41651, build 7345, released August 29, 2026.

On macOS 26.5.2 (build 25F84), the built-in browser was enabled/configured and Chrome was not explicitly requested. In thread 01a04e47-750f-72f1-854b-b8eb0b4a7ab9, a generic HTTPS URL operation nevertheless selected the Chrome browser extension, and the URL opened in Chrome.

Verified observations

• The initial generic URL-routing operation selected the Chrome backend with browser type extension.
• The URL opened successfully in Chrome.
• After I reported the browser-selection problem, the agent explicitly selected the built-in-browser backend (iab) and opened the same destination successfully.
• Two later built-in-browser tests also succeeded because that explicit selection persisted.
• A later attempt to reproduce the original Chrome route failed immediately with Browser is not available.

Assessment

This looks like an application-level browser-surface routing issue rather than a macOS default-browser issue. The generic URL path may be selecting an available Chrome extension instead of honoring the configured in-app-browser preference. Persistent browser binding may then make later requests appear corrected after the user reports the problem.

The original behavior was observed in one prior session. The later successful in-app-browser operations were explicit, so they should not be treated as a clean independent reproduction or proof that the underlying routing defect was fixed.

What steps can reproduce the bug?

Observed sequence

The following is a privacy-preserving reproduction outline based on the observed session; the original behavior was not independently repeated in a fresh session.

1. Open the macOS app branded ChatGPT.
2. Enable/configure the built-in browser / Browser Use setting.
3. Make sure the ChatGPT Chrome extension is available, but do not explicitly request Chrome.
4. Start a fresh ChatGPT/Codex task.
5. Ask the agent to open a benign HTTPS URL.
6. Observe which browser surface is selected.
7. If Chrome is selected, mention the browser-selection problem in the same task.
8. Ask the agent explicitly to use the built-in browser.
9. Observe that the built-in browser works after explicit selection.
10. Repeat the generic URL request and check whether the explicit browser binding is being reused.

The original test used a ChatGPT URL, which is intentionally omitted for privacy. The original session identifier was 01a04e47-750f-72f1-854b-b8eb0b4a7ab9.

What is the expected behavior?

Expected behavior

When the ChatGPT in-app browser is enabled, it should be the default browser surface for generic URL operations.

Chrome should be selected only when the user explicitly requests Chrome, chooses Chrome in the UI, or confirms a fallback.

The browser-selection preference should apply consistently to generic URL requests. Later explicit browser selection should not conceal the original routing failure. If a selected browser becomes unavailable, the runtime should clear or report the stale binding deterministically.

Additional information

Environment

• Application name shown in About dialog: ChatGPT
• About dialog text: Powered by Codex & OWL
• Version: 26.825.41651
• Build: 7345
• Release date shown in About dialog: August 29, 2026
• Platform: Darwin 25.5.0 arm64 arm
• macOS: 26.5.2 (build 25F84)

Technical correlation

• Feedback/session thread ID: 01a04e47-750f-72f1-854b-b8eb0b4a7ab9
• Token/context usage: not included in this public report.

Related report

This may be related to #27534, which reports Chrome being selected when the in-app browser is explicitly requested and Chrome Use is disabled. This report differs because it concerns a generic URL request while the in-app browser was configured and Chrome was not explicitly requested.

Privacy

No browser logs, ChatGPT session logs, local paths, directory names, credentials, device identifiers, network identifiers, uploaded files, or public ChatGPT share URLs are attached. The original URL and local filesystem details are intentionally omitted.

Start with a fresh ChatGPT/Codex task on macOS, with the in-app browser enabled and Chrome available, and reproduce a generic HTTPS URL request without explicitly choosing a browser. Trace the generic URL-routing path and any persistent browser binding; done means the configured in-app browser is selected by default, Chrome requires explicit selection or fallback, and unavailable bindings are reported or cleared deterministically.