codex - 💡(How to fix) Fix In-app Browser enabled but browser automation tool unavailable in mobile-created Codex thread

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

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

Environment

  • Product: Codex App / Codex cloud thread
  • Codex version: codex-cli 0.131.0-alpha.9
  • OS: macOS
  • Thread origin: created from mobile after updating Codex, then continued on desktop
  • Browser setting: enabled in Codex settings
  • Target domain allowlisted in Browser settings: https://calcpcbplus.hasil.gov.my

Issue

The Codex in-app Browser is enabled in Settings, and the target domain is allowlisted. However, inside this thread Codex cannot access the actual Browser automation tool.

Tool discovery only exposes GitHub tools. The Browser plugin/skill metadata appears available in the session, but the callable browser automation endpoint is missing from the active tool list.

Expected behavior

A thread with Browser enabled should expose usable in-app browser automation tools, including when the thread was created from mobile and later continued on desktop.

Actual behavior

Codex cannot open or control the in-app Browser from this thread. It can see Browser-related skill/plugin metadata, but no callable Browser control tool is available.

Impact

This blocks official website validation work that requires Codex to open and interact with the HASiL calculator site:

https://calcpcbplus.hasil.gov.my/HITS_CE/x2026?FRS_REC=True&lang=EN

The user also spent quota/time diagnosing what appears to be a platform/tool capability injection issue rather than doing the intended validation work.

Notes

This may be related to mobile-created threads after a Codex update missing Browser capability injection. Please investigate whether Browser capability assignment is being snapshotted incorrectly for mobile-originated Codex threads.

If this is confirmed as a product-side issue, please advise whether the affected user can receive additional usage quota/credits for the time spent diagnosing it.

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

A thread with Browser enabled should expose usable in-app browser automation tools, including when the thread was created from mobile and later continued on desktop.

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 In-app Browser enabled but browser automation tool unavailable in mobile-created Codex thread