Codex dot fails to read user-created threads with 'unsupported placement' errors

Takanashi-Rikka1 · ghdev · 2026-10-10

Issue #52873 on openai/codex: with the Windows desktop app connected, dot fails to read user-created Codex threads, returning "unsupported placement format version" / "unsupported placement region" errors. This contradicts the official announcement that users can follow up on existing Codex threads — tasks created by dot work, but user-created threads don't.

Reproduction: connect the desktop, copy a codex://threads/<threadid> link, ask dot to read it; the cloudthreads.read call fails before returning content. Updating the app and reconnecting the machine did not help.

Original post →

More from coding & agent

coding & agent channel →