Codex 28 · Theme · #35

Dot connection instability in Codex

11people describe this

11 on X

1 win · 11 problems · first reported 7 Oct 2026

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 yet

No recorded announcement has answered this yet.

In their words

What people said

Problem
Any chance the dot call wont disconnect when the screen locks. I’m being forced to other LLMs due to this issue.

@MarcMesserX on X ↗ · 25 Oct 2026
Problem
Tibo what’s happening to my dot its reconnecting and disconnecting all the time simce yesterday??

@LourensDonavin on X ↗ · 19 Oct 2026
Problem
Why am I unable to make call to my dot? Is it a known bug - (in Singapore region).

@aSaubhagya on X ↗ · 10 Oct 2026
Problem
Why can't my Dot link with Codex on my local computer? I'm unable to use Dot to orchestrate the local Codex.

@AngelKittybing on X ↗ · 9 Oct 2026
Problem
wtf is up with the recent update?? the app on both of my machines is fucked. Dot responses dont show up until I follow up after thinking it doesnt respond, and my codex's wont connect to each other dav 5 is a wash. give us a banked reset plz

@EthanSwzr on X ↗ · 9 Oct 2026
Problem
I've been experiencing frequent connection issues when trying to use my dot in Codex. It often fails to connect, even after multiple attempts, which really disrupts my workflow. Is this a known issue? Are there any plans to improve connection stability?

@kVUOLEzytNspt60 on X ↗ · 9 Oct 2026
Problem
instead can you get dot call fixed its 36 hours its not connecting. call failed every time

@he_the_mystery on X ↗ · 8 Oct 2026
Problem
Somehow, at least for me, my Dot cant reach my pc after the last update

@mazoboy on X ↗ · 8 Oct 2026
Win
So this issue was just fixed by Astra i switched the model on the codex session from gpt6.1 sol to Astra and some how it re-established the connection with my dot agent on code . Astra is truly a fantastic beast

@Kamar_202 on X ↗ · 8 Oct 2026
Problem
So my dot agent can’t reach file & folders on my Mac, it needs a session on codex 2 do it & they used 2 communicate via a thread on d codex app bt after an upd8 dat communication broke now dey are using a jira comment 2 communicate. Is der anytime we can do 2 correct this.

@Kamar_202 on X ↗ · 8 Oct 2026
Problem
Hi Tibo, since DevDay I've spent more time fixing CLI/MCP connections between dot, Codex and other tools than actually creating. Connections work one day and fail the next. It's exhausting. I love the idea of dot, but I need it to reliably get work done. Could you help?

@dporriimse216 on X ↗ · 8 Oct 2026
Problem
Thanks for the reset, BUT I can’t use it since I’m dealing with multiple codex bugs. One is DOT can’t connect to codex chats. It’s returning error message “unsupported placement format version 3”.

@LoneStarSignsTX on X ↗ · 7 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.

What happened with “Dot connection instability in Codex”?

0 / 1200

Tell us a little more — at least 20 characters.

Your words stay yours.

AI reads your draft as you type. Only what you publish is public. Privacy

Not sure where to start?

Think of the last task you tried. What were you doing, what happened, and what would have helped? You can also say you haven't tried a change yet.

01
What you said

Read as you type: a win, a problem or an idea, and the words that carry it.
Ready when you are
Who else had it

The theme your words join, and how many people on Rantr and X described it.
Where OpenAI stands

Shipped, reset, or not addressed yet, from the recorded announcements.
What to do now

A step the announcements make possible for you, when there is one.

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

26 Oct 2026, 04:50 UTC

“Call stays connected on lock” was merged into this theme: JEV judged them the same problem.
11 Oct 2026, 09:15 UTC

“Responses visible after follow-up” was merged into this theme: JEV judged them the same problem.
9 Oct 2026, 04:14 UTC

Renamed from “Connection drops during Codex sessions” to “Dot connection instability in Codex” as more people described it.
9 Oct 2026, 04:14 UTC

“Unsupported placement format version” was merged into this theme: JEV judged them the same problem.
9 Oct 2026, 04:13 UTC

“Connection restored after model switch” was merged into this theme: JEV judged them the same problem.
9 Oct 2026, 04:13 UTC

“Device connection lost after update” was merged into this theme: JEV judged them the same problem.
9 Oct 2026, 04:12 UTC

“Call connection failures” was merged into this theme: JEV judged them the same problem.

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