Codex on Windows drops execution-location selector, blocks localhost access in new Work sessions
eurus0919 · ghdev · 2026-11-21
A ChatGPT Desktop for Windows (MSIX 26.1117.4957.0) user reports that new Codex Work sessions no longer offer the execution-location selector, even with a local workspace selected.
- Sessions can still access files in the selected workspace via execution tools
- But connections to a localhost browser-automation endpoint fail, breaking the previous local Work workflow
- The app also threw a main-process error: Connection for host ID local not found
The report complements related issues #62918/#62912/#62722 by documenting the gap between filesystem access and direct local service connectivity. The author asks OpenAI to clarify whether local Work execution is still supported, and to explain in the UI if it has been removed rather than silently dropping the selector.
More from coding & agent
- Chinese devs vent: app store rejections and copycats are just the norm — tinyfool · 2026-11-22
- Compacting Early and Often Boosts Agent Accuracy While Cutting Cost and Runtime — zainhas · 2026-11-22
- Astra 6.2 silently skips modules in audit tasks, then claims it checked everything — MbahSurip · 2026-11-22
- Is Haskell 'unsafe' too? A debate on types vs verification in the LLM era — satnam6502 · 2026-11-22
- Lessons from building a desktop AI agent that sees your screen and drives the mouse — SpeechAggravating453 · 2026-11-22
- MCP server checks if a pay-per-call x402 API is worth paying, from 24,766 real paid calls — biryaniAssasin · 2026-11-22