›_ Codex Issues
Codex Issues / #19373

Codex in-app browser cannot complete D&D Beyond Google sign-in

Open 💬 4 comments Opened Apr 24, 2026 by rondavis007
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

The Codex in-app browser cannot complete Google OAuth login on D&D Beyond. Clicking "Sign in with Google" does nothing from the user's perspective, and browser automation cannot interact with the Google sign-in control because it is inside a cross-origin iframe.

Steps to reproduce

  1. Open the Codex desktop app.
  2. In the in-app browser, navigate to https://www.dndbeyond.com/my-campaigns.
  3. Click Sign in.
  4. Click Sign in with Google.

Expected behavior

The Google OAuth sign-in flow should open and allow the user to authenticate, so the agent can continue with the user's authorized task.

Actual behavior

The Google sign-in button does not work in the in-app browser. In this session, automation reported:

Unable to translate Input.dispatchMouseEvent in the in-app browser: Input targets inside cross-origin or inaccessible iframes are not currently supported in the in-app browser

The fallback to a Wizards username/password login is not viable for users whose D&D Beyond account must use Google sign-in.

Impact

This blocks agent workflows that require logging into sites where Google OAuth is the only usable login method. In this case, the agent could not access D&D Beyond campaign pages to update a Notion character database with D&D character levels.

Environment

Additional context

The actual browser/Chrome backend was not available in this session, so there was no working fallback to a browser where the user was already signed in.

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #19276

Powered by Codex Action

rondavis007 · 4 months ago

Duplicate of #19276

vanjaoljaca · 16 days ago

Additional macOS reproduction with TikTok third-party sign-in in the Codex in-app browser.

Environment:

  • Codex desktop app 26.803.61601 build 6396
  • macOS 15.7.7
  • Browser surface: Codex in-app browser
  • Site: TikTok

On TikTok's login screen:

  1. Clicking the Google OAuth option opened a blank popup window.
  2. Clicking the Facebook OAuth option also opened a blank popup window.
  3. Neither popup loaded a usable provider sign-in flow or returned authentication to TikTok.

A password-based login was attempted separately and TikTok immediately returned Maximum number of attempts reached. Try again later. after one manual attempt, while the account remained authenticated and functional in the TikTok iOS app. That provider-side restriction may be separate, but Google and Facebook OAuth were independently unusable because their popup windows were blank.

Expected behavior: third-party OAuth popups should render and return to the originating site. If the in-app browser cannot support a provider's OAuth flow, Codex should securely hand authentication off to the system browser or an existing signed-in browser session, then restore the original workflow with a clear status.

Private account details are omitted. A sanitized task transcript can be provided if maintainers need additional diagnostics.

sephmartin · 14 days ago

Additional macOS reproduction: this is not Google-specific.

The Codex in-app Browser opens blank/white popup windows for Google, PayPal, and other third-party popup-based flows. The popup shell appears, but the provider page never renders and the flow cannot return to the originating page.

This suggests a generic popup/new-window/WebView handoff issue rather than a provider-specific OAuth problem.

Environment:

  • macOS 27.0, arm64
  • ChatGPT/Codex desktop build 151.0.7922.137
  • Codex in-app Browser