r/OpenAIDev

Has anyone seen this Codex / ChatGPT error before?

RuntimeError: The invoking thread is not attached to an active Aeon

It started today (Oct 7) while using a ChatGPT Dot/assistant that had previously been able to create and control Codex tasks on my Windows PC.

What is strange:

• Codex itself still works if I talk to it directly
• Normal conversation with the Dot works
• The Dot could still read an existing Codex task
• But the Dot cannot send new instructions to that task
• It cannot create a new Codex task
• It also cannot list my connected computers

All three operations return the same active Aeon RuntimeError.

Before this happened, my PC was shown as connected, attached and authorized.

I already tried restarting the PC, reopening ChatGPT, updating the app, creating a new Codex task and re-confirming permissions.

I searched for the exact error but couldn't find a single public report of it.

Has anyone encountered this before, especially with Dots/Work → Codex integration?

Could this be a broken server-side association between the assistant conversation and its Codex execution context?

Direct Codex still working makes me think the Codex service itself is fine.

UPDATE 2 — Aeon error is gone, but local execution is still broken

The original active Aeon error has disappeared. My Dot can now see the connected PC and create a local Codex task again.

However, even a simple Get-Location command fails with:

helper_unknown_error: setup refresh had errors

I restarted ChatGPT and reconnected the PC, but local execution still fails.

Anyone else seeing this after the Aeon incident recovery?

Between the accidental Astra threads and the unreliable output from 6.1 SOL, I see no meaningful efficiencies being given to us. Tibo owes us.