Forumics logo Forumics
Issue 01

Back to issue

All Codex known issues

CLAIM C123 Supported 2026-11-14

GitHub issue #57721 in openai/codex, opened 2026-10-28 by fengzee, records a report that on macOS with Codex desktop app 26.1023.50603 and the Android ChatGPT app connected through Codex/Remote, a new chat created entirely from the phone cannot access the connected Mac's Chrome browser and reports Local browser use is disabled in Work settings although the setting is enabled and both devices use the same account/workspace; sending a message in the same chat from the Mac starts browser access, after which the phone can use it, while chats created on the Mac work when continued from mobile, and restarting both apps and creating a fresh mobile chat does not fix the failure; the report expects mobile-created remote chats to initialize browser access just like desktop-created chats and says initialization failures should not be reported as a disabled setting.

Verbatim Excerpts from Cited Records
“A new chat created entirely from mobile cannot access the connected Mac's Chrome browser.”
— fengzee · openai/codex (issue 57721 opening body, Issue and impact section) · 2026-10-28T12:35:44Z ·GitHub Issue ↗
“The setting is enabled, and both devices use the same account/workspace.”
— fengzee · openai/codex (issue 57721 opening body, Issue and impact section) · 2026-10-28T12:35:44Z ·GitHub Issue ↗
“This prevents users away from their computer from starting new browser-based tasks remotely.”
— fengzee · openai/codex (issue 57721 opening body, Issue and impact section) · 2026-10-28T12:35:44Z ·GitHub Issue ↗
“Mobile-created remote chats should initialize browser access just like desktop-created chats, subject to the same permissions.”
— fengzee · openai/codex (issue 57721 opening body, Expected behavior section) · 2026-10-28T12:35:44Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 23 comments were read. robertorusso1234-boop (2026-10-29, Windows 11 with iOS), mr-ashawa (2026-10-29, Windows with Android), jrrmarketing (2026-10-29, macOS diagnosis), komuken (2026-10-29, macOS), rennavationstudios-bit (2026-10-29, Windows), akshaygulabrao (2026-10-29, macOS 26.6.2), nbne61-create (2026-10-30, iPhone with Mac), longcat (2026-10-30, Windows with iPhone), nabioz (2026-10-31, Windows), BIG-legion (2026-11-01, Windows with Android), natha909 (2026-11-01, Linux desktop preview), maciej (2026-11-01, macOS), Bjarkinn (2026-11-01, Windows), KORDayDream (2026-11-02, Windows with Android), righttang (2026-11-03, macOS), and kurtyan (2026-11-09, Mac-to-Mac control) independently reproduce mobile- or remote-created chats reporting browser access disabled while the setting is enabled. nbne61-create (2026-10-30) confirms the same-chat desktop-message workaround in the exact failing chat. secheverrianogal-beep (2026-11-03) refines the recovery boundary: merely displaying the affected chat in the desktop app and completing thread/resume restored Chrome access without a desktop message. righttang (2026-11-13) offers a SessionStart hook workaround that auto-opens the conversation in the desktop app. rohan20 (2026-11-08) reports a related browser-availability failure without confirming the same mobile-created trigger. No maintainer fix and no retraction of the report appear in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #57721 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.

See also: Codex vs Cursor head-to-head comparison on 9bests