Codex desktop bug: dot fails to read threads with 'unsupported placement regions'
Mills713 · ghdev · 2026-10-09
A new issue (openai/codex #52331) reports that dot in the ChatGPT desktop app (Powered by Codex & OWL, on a ChatGPT Pro 100 plan) cannot read some Codex threads despite showing Connected: errors cite "unsupported placement region 6/14" for post-cutover thread IDs and "unsupported placement format version 3" for an older one. Listing local desktop projects also fails with DesktopProjectsUnavailableError. Only some conversations are affected; restarting, revoking/regranting access, and creating fresh projects don't help. Full repro steps via deeplink thread IDs are included; 4 comments so far.
More from coding & agent
- Ethan Mollick's new book charts 30 months of AI progress, from cyborg to conjurer work — rseroter · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Jensen Huang details Vera Rubin agentic stack: NVL72, MGX, CMX and RTX — rohanpaul_ai · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23
- Capy 0.5.0 lets Claude Pro/Max subscribers reuse their plan quota, adds OIDC cloud access — garrytan · 2026-10-23