codex - 💡(How to fix) Fix Codex in-app browser cannot complete D&D Beyond Google sign-in [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19373Fetched 2026-04-25 06:10:29
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×2

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.

Root Cause

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.

Fix Action

Fix / Workaround

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

Code Example

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
RAW_BUFFERClick to expand / collapse

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.

extent analysis

TL;DR

The Codex in-app browser's inability to interact with cross-origin iframes prevents Google OAuth login on D&D Beyond, and a potential workaround is to use an external browser for authentication.

Guidance

  • Investigate using an external browser for Google OAuth authentication, as the in-app browser's limitations may be unavoidable.
  • Consider implementing a feature to detect when an external browser is available and use it for authentication when necessary.
  • Look into potential workarounds for handling cross-origin iframes in the in-app browser, such as using a proxy or modifying the browser's security settings.
  • Evaluate the feasibility of using a different authentication method, if possible, to avoid relying on Google OAuth.

Example

No code example is provided, as the issue is more related to browser functionality and authentication workflows.

Notes

The solution may require significant changes to the Codex desktop app's architecture or authentication flow. Additionally, using an external browser may introduce new security or usability concerns that need to be addressed.

Recommendation

Apply workaround: Use an external browser for Google OAuth authentication, as it seems to be the most feasible solution given the in-app browser's limitations.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

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.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Codex in-app browser cannot complete D&D Beyond Google sign-in [2 comments, 2 participants]