Repository navigation
In-app browser opens Google result links in a blank new tab #46610
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.915.31945
What subscription do you have?
Plus
What platform is your computer?
Darwin 27.0.0 arm64 arm
What issue are you seeing?
On macOS, links opened from Google search results in the Codex App in-app browser create a new tab whose content area stays blank. The page itself is reachable: pasting the destination URL directly into the address bar of a new tab renders it normally. Reloading the blank tab does not help.
Example: a Google result for https://brew.sh/ko/ opened as a blank tab. Manually navigating to https://brew.sh/ko/ displayed the Homebrew page normally.
What steps can reproduce the bug?
- Open the Codex App on macOS.
- In the in-app browser, search Google for a page.
- Click an external search result that opens in a new tab.
- Observe that the new tab stays blank.
- Copy the destination URL and paste it directly into the address bar of a new tab. The page renders normally.
What is the expected behavior?
The destination page should render normally when opened by clicking a Google search result, just as it does when the same URL is entered directly.
Additional information
No error is shown in the blank tab. Reloading the tab does not resolve the issue.
Activity
iamhectorlopez commentedon Sep 21, 2026
Additional macOS reproduction on 26.915.31945 (build 9922): this also affected a link from a local HTML document library to its same-origin HTML/PDF.js reader, rather than a Google result.
uname -mprs:Darwin 25.6.0 arm64 arm.Info.plist(com.openai.codex).The link uses the usual pattern:
(The path and document identifier above are sanitized placeholders.)
Observed comparison
This appears to extend the new-tab symptom beyond Google links. The current workaround is same-tab navigation or a fresh directly navigated tab. The underlying cause remains unconfirmed.
Native PDF URLs also produced a separate blank-viewer symptom on this machine, reported with a public PDF under #44132. This comment concerns an HTML reader page whose entire new tab fails to display, not just native PDF rendering.