GitHub issue #29915 in openai/codex, opened 2026-06-24 by andrewsohrabi, records a report that permission and approval mode selection is not reliably persisted for new threads or already-loaded existing threads: on a new thread, choosing a non-workspace mode such as Full access falls back to workspace after the thread starts and the first prompt executes, while the picker still looks selectable before submission; on an existing loaded thread, changing approval and permission mode through resume appears to work in the UI, but the live thread keeps the old effective settings; the report proposes two linked fork commits as fix candidates, one routing loaded-thread resume overrides through the validated thread-settings path and one exposing permissions plus activePermissionProfile for thread start, resume, and fork in the stable protocol fixtures, and reports focused local tests passing.
Verbatim Excerpts from Cited Records
“Permission / approval mode selection is not reliably persisted for either new threads or already-loaded existing threads.”
“On an existing loaded thread, changing approval / permission mode through resume appears to work in the UI, but the live thread keeps the old effective settings.”
“On a new thread, the permission picker allows selecting non-workspace options such as **Full access**, but after the thread starts / first prompt executes, the effective state falls back to **workspace**.”
“The dropdown state can therefore look selectable before submission while the running thread state does not reflect the selected mode.”
Counter-record: Issue open as of the fetch; 29 comments were read. github-actions[bot] (2026-06-24) flagged #29586 and #28776 as potential duplicates; the author replied it is not a duplicate. The author (2026-06-25) posted two fork commits as suggested fix candidates, a loaded-thread backend fix and a new-thread schema and client-contract fix, with a compare link, and reported focused local tests passing. Independent reproductions followed across platforms and builds: metrovoc (2026-08-03, macOS, with a private feedback upload), BeautyToolsAU (2026-09-15, Windows, where Full Access only took effect after toggling to Require approval and back), edwardswhiskeyblues-alt (2026-10-06, Windows, two existing threads silently changed from Full Access to Approve for me), info618 (2026-10-10, macOS, existing sessions kept workspace-write after Approve for me was selected and the app restarted), miloszjader-create (2026-10-15 and 2026-10-16, macOS, a named custom permission profile with persisted turn_context evidence showing the profile present in one turn and absent in the next, and a post-update reproduction on the newer build), 5edges-engineering (2026-10-15, an existing remote thread on Codex CLI 0.157.1), ViciousSeagull (2026-10-17, Windows), ramonalarcon4 (2026-10-18, Windows, with a verified CLI workaround), and liby (2026-10-19, macOS, a follow-up dropping the development profile and removing read-only protections for workspace env paths). virajchoudhary (2026-10-13, 2026-10-14, and 2026-10-21) implemented a bounded local candidate on a fork, published the tested commit, and reported on 2026-10-21 that the loaded-resume and fork defects it covers are not superseded at merged upstream 57232f111c50e59d748d010048c9e10832ed79d7. StutteringJohnMelendez (2026-10-07) asked maintainers for a status update, including the supported contract for cloud-backed conversations. The latest comment, 485fm4667h-art (2026-11-13), asks for a supported recovery when the permissions selector disappears after the first message. 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 #29915 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.