Windows: in-app browser hangs during GitHub Google OAuth and can crash controlled Chrome tabs

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

26.602.4764.0

What subscription do you have?

Unknown (ChatGPT account; the app does not display the subscription tier)

What platform is your computer?

Microsoft Windows NT 10.0.19045.0 x64

What issue are you seeing?

The Codex in-app browser cannot complete GitHub sign-in through Google OAuth. On the GitHub login page, clicking Continue with Google leaves the button stuck as Continuing with Google... and disabled. The OAuth flow never returns to GitHub and the user cannot leave the state normally.

The GitHub login tab then disappears from the controlled in-app browser session, leaving only an about:blank#codex-browser-sidebar-attach-token=... placeholder.

When falling back to the Codex Browser extension in an already authenticated Chrome profile, Browser operations repeatedly stall. The controlled GitHub tab first shows Chrome Page Unresponsive, then crashes with Aw, Snap! and RESULT_CODE_HUNG.

Relevant errors observed in the same Codex session:

• POST https://ab.chatgpt.com/v1/initialize: Timeout of 10000ms expired
• POST https://ab.chatgpt.com/v1/rgstr: Timeout of 10000ms expired

What steps can reproduce the bug?

1. Open the Codex in-app browser on Windows.
2. Navigate to https://github.com/openai/codex/issues/new?template=1-codex-app.yml while signed out.
3. On GitHub sign-in, click Continue with Google.
4. Observe that the button stays at Continuing with Google... and the OAuth redirect/popup does not complete.
5. Inspect controlled tabs: the GitHub login tab can disappear, leaving only an attachment placeholder.
6. As a fallback, connect the Codex Browser extension to a Chrome profile already signed into GitHub.
7. Perform several form read/fill operations.
8. Observe repeated 10-second request timeouts, then Chrome Page Unresponsive, followed by RESULT_CODE_HUNG.

What is the expected behavior?

Google OAuth should complete and return to the original GitHub URL. If embedded OAuth is unsupported, Codex should open authentication in the system browser and preserve the return URL. Telemetry or analytics request failures must not block page interaction or hang the controlled renderer.

Additional information

Occurred June 8, 2026 around 12:15-12:29 Asia/Shanghai. A Codex in-app feedback report was submitted with the current session logs at 12:29. Screenshots captured the stuck OAuth state, Page Unresponsive, and RESULT_CODE_HUNG. Personal email and local paths are omitted from this public issue.