Codex 28 · Theme · #46
Local Codex thread access
10people describe this
10 on X
X replies to the promise post are counted apart from Rantr votes. “This happened to me too” adds your browser to this theme on Rantr, once.
Where OpenAI stands
Not addressed yetNo recorded announcement has answered this yet.
In their words
What people said
- Problem
Did this regress? Dots access to existing threads seems to no longer work..
@OneStoryRoad on X ↗ · 12 Oct 2026
- Problem
cant go a day without "Thread not found error" as well
@SwanCourier on X ↗ · 12 Oct 2026
- Idea
Docs say dots can continue existing local Codex tasks, but connecting a computer doesn't grant access to every old chat. I'd name one specific thread first, with the desktop app open. Less robot hide-and-seek 😄https://t.co/oMvBVStfBI
@dotsMCLOVIN on X ↗ · 11 Oct 2026
- Problem
Can Dots read existing threads on codex? Mine doesn’t seem to be able to from my local machine.
@NickKhana on X ↗ · 11 Oct 2026
- Problem
Why can’t it read any of my local codex threads on desktop? Biggest miss imo
@neurajordan on X ↗ · 10 Oct 2026
- Problem
Hi Tibo, this still fails for me on Windows. My PC is connected and access enabled. Reading an existing local Codex thread returns “unsupported placement region 10”; messaging it returns “CloudThreadNotFoundError”. Is this a known issue or still rolling out?
@xiangwenyhc on X ↗ · 10 Oct 2026
- Problem
My dot is still getting an “unsupported placement format” trying to read threads :(
@qtomaro109 on X ↗ · 10 Oct 2026
- Problem
Hi Tibo, my dot can directly list projects on my connected Mac, but can't read existing local Codex threads: “unsupported placement format version 1” (also v2). A task on the Mac can read them. Is this a known issue with the new thread support? Any fix?
@huaye37 on X ↗ · 10 Oct 2026
- Problem
Dots could do this from day one. It still can't read any chats/threads which is inane. The vm is has gets JavaScript restricted after two repetitive tasks (not by accident) , I could go on and on, dots has been so underwhelming it's an UNDERstatement. Love the tech but the tech…
@TENTHDEMENSION on X ↗ · 10 Oct 2026
- Problem
Could the team look at dot/local Codex thread access? Direct reads of existing Mac threads still fail; a previously working relay lost its tools. Fresh relay reads work, but the old one remains broken. Repros: https://t.co/cpVeV0bifm https://t.co/rN9Igb8b76
@ShugeiWorkshop on X ↗ · 6 Oct 2026
Your experience
Had this too? Say what happened.
JEV reads your words as you type and shows which theme they belong to. It may place them in another theme if that fits better.
Status
Where OpenAI stands
“Shipped” means an announcement was linked to the theme by AI, not that the problem is fixed for everyone. “Not addressed yet” means no recorded announcement was linked; it is not proof that nothing changed.
No recorded announcement has been linked to this theme yet.
Corrections
Changes to this theme
-
“Specific thread needed for connection” was merged into this theme: JEV judged them the same problem.
-
Renamed from “Thread format compatibility mismatch” to “Local Codex thread access” as more people described it.
-
“Old relay access remains unavailable” was merged into this theme: JEV judged them the same problem.
Share
Share this theme
Follow
Follow this theme by email
We send a confirmation link first; nothing else is sent until you confirm. Then at most one email a day, only when the theme changes.
X thread: 2769 replies to the promise post collected (4 Oct 2026 – 26 Oct 2026): 2555 placed in a theme and 214 set aside as off-topic or unsafe. X replies are found by search and each one is checked against its public post on X. Last read: 26 Oct 2026, 23:46 UTC. Not every reply is read.
← Every theme