Repository navigation
Open
Labels
appIssues related to the Codex desktop appIssues related to the Codex desktop appbugSomething isn't workingSomething isn't workingsandboxIssues related to permissions or sandboxingIssues related to permissions or sandboxingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Description
What version of the Codex App are you using (From “About Codex” dialog)?
OpenAI.Codex 26.1117.4957.0 (Windows Store/MSIX, app version 26.1117.41037, build 29803, bundled CLI 0.171.0-alpha.13)
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Windows 11 Home 64-bit (10.0.26200)
What issue are you seeing?
Summary
On Windows ChatGPT Desktop (OpenAI.Codex 26.1117.4957.0), starting a new Work chat shows the bottom-left permissions selector before sending the first message, but:
- The bottom-right run-location selector ("On your computer" / Local vs Cloud) is completely missing from the Work home composer, even though
work-run-location-v1is set to"local". - Sending the first message routes the conversation to Cloud/TPP (
/c/<conversationId>,active-tpp-turn/hostId=durable). - Immediately after the first message is sent, the bottom-left permissions selector disappears from the conversation view, and the active session remains restricted instead of honoring the configured Full Access permissions.
Actual behavior
- Work Home forces
effectiveLocation = "cloud"withcanChooseLocation = false(ignoringwork-run-location-v1 = "local"), so the bottom-right Local option does not render at all. - Once the message is sent and the view transitions from Home (
/) to the ChatGPT conversation route (/c/<conversationId>), the bottom-leftPermissionsModeDropdowndisappears completely and the effective session remains restricted. - By contrast, existing
/local/<threadId>Codex threads on the exact same machine retain the bottom-left permissions selector and run withsandbox_policy: danger-full-accessandapproval_policy: never.
What steps can reproduce the bug?
- Configure Full Access locally (
config.tomlhassandbox_mode = "danger-full-access",approval_policy = "never",approvals_reviewer = "user",[windows] sandbox = "elevated";C:\ProgramData\OpenAI\Codex\requirements.tomlhas no policies; global state hasagent-mode-by-host-id: {"local": "full-access"}andwork-run-location-v1: "local"). - Open ChatGPT Desktop on Windows and start a new Work draft on the Home screen.
- Observe that the bottom-left permissions control is visible before sending, while the bottom-right Local/Cloud run-location selector is not shown.
- Send a message (e.g. a simple prompt).
What is the expected behavior?
- Users who want local execution from Work should be able to choose "On your computer" (Local) or have
work-run-location-v1 = "local"respected. - After sending the first message, the bottom-left permissions control should remain visible/inspectable and the session should honor the user's configured permission mode rather than falling back to restricted permissions.
Additional information
- Related issues: Windows ChatGPT Work: permissions selector disappears after chat starts and node_repl is unavailable #50317, [ChatGPT Desktop][Work][macOS] permissions control disappears after first message (local execution) #55290, Windows desktop: Full access selected, permission controls disappear, and Git operations remain blocked. #56882, macOS Desktop 26.1027.51404: Full access control disappears after chat creation; effective session remains restricted #58677, macOS Codex desktop: permissions selector disappears from existing thread, process checks sandboxed despite prior Full access #60109, [Windows / ChatGPT Work] Permission selector missing across chats despite Full access being enabled; SSH resolves to denybin stub #61501.
- No managed enterprise/admin policy is present (
C:\ProgramData\OpenAI\Codex\requirements.tomlcontains comments only). - Desktop logs show new Work drafts from Home creating
local-chatgpt:<id>//c/<id>(active-tpp-turn,hostId=durable) sessions whiletpp-local-executor(codex.exe exec-server --remote) is connected.
Reacted by RAHUL REX, dOHMotik and Freevatar
Metadata
Metadata
Assignees
Labels
appIssues related to the Codex desktop appIssues related to the Codex desktop appbugSomething isn't workingSomething isn't workingsandboxIssues related to permissions or sandboxingIssues related to permissions or sandboxingwindows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems
Activity
github-actions commentedon Nov 21, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
RahulRex0 commentedon Nov 21, 2026
same thing in Mac
freevatar commentedon Nov 21, 2026
same on Linux