GitHub issue #60058 in openai/codex, opened 2026-11-07 by bradcarroll, records a report that in ChatGPT desktop on Windows, Work mode, app version 26.1103.32239, the new-chat Work composer shows Full access but the resulting conversation's execution context reports workspace-write with restricted network access, and the Full access control is visible only before starting the chat and then disappears, leaving no visible in-thread way to inspect or correct the selected mode; a harmless, explicitly authorized SSH check fails at the first jump-host TCP connection, before SSH authentication, with the SSH child process returning exit 255; fully restarting the ChatGPT desktop app did not change the result, and returning to the same conversation through the web interface produced the same result from its local command runner; the report lists related reports #57671 and #59528 and asks for consolidation with an existing issue if appropriate.
Verbatim Excerpts from Cited Records
“The new-chat Work composer shows **Full access**, but the resulting conversation's execution context reports **workspace-write with restricted network access**.”
“The user reports that the Full access control is visible only before starting the chat and then disappears, leaving no visible in-thread way to inspect or correct the selected mode.”
“A harmless, explicitly authorized SSH check fails at the first jump-host TCP connection, before SSH authentication.”
“Fully restarting the ChatGPT desktop app did not change the result.”
Counter-record: Issue open as of the fetch; 18 comments were read. github-actions[bot] (2026-11-07) flagged #59528, #58677, #59605, and #59976 as potential duplicates. grtninja (2026-11-07) determined this is the same defect as #58677 and #59528, noting #59976 was already closed as a duplicate of #59528 and #58677, and #59605 is related but not a strict duplicate. caibirdme (2026-11-07) and elvrik (2026-11-07) confirm the same failure, with caibirdme noting it also occurs on macOS. huemer28 (2026-11-10) reproduces the SSH symptom on Windows and asks for a fix date or workaround; Anoninthonesty2 (2026-11-10) reports the same issue plus a separate model-version error in VS Code. nishmark (2026-11-11) reproduces it on Windows and reports selecting "On your computer" as the execution location resolved the access issue, while caibirdme (2026-11-11) reports that workaround does not work for them. JERRY10086-web (2026-11-11) reports only newly created Work chats lose the Full Access icon. Agiblin (2026-11-11) reproduces the SSH failure on Windows 11 25H2 with exit 255. huemer28 (2026-11-11) confirms local execution restored DNS and SSH on their machine and calls the cloud-session behavior unresolved. bestmoversdmv12 (2026-11-11) adds a related Windows SSH report with feedback ID 6af39a01-3a60-8191-80ef-86e057e44014. wendefeuer (2026-11-12) reports SSH worked until a Codex update from 26.1103.7773.0 to 26.1106.6628.0, after which it failed. my-space-repo (2026-11-13) and hmuaz (2026-11-13) confirm the "On your computer" execution-location workaround restores SSH and local access. YoleYu (2026-11-13) suggests switching from ChatGPT to Codex in the app. 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 #60058 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.