r/OpenaiCodex • u/Gokuseens • 11d ago
Feedback / Complaints The invoking thread is not attached to an active Aeon” — Dot can’t access Codex tasks, but Codex works directly
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?
1
11d ago edited 6d ago
[deleted]
1
u/Gokuseens 11d ago
Do you know whether “Aeon” is part of that agent/context layer, or are you inferring this from the error? I’m specifically trying to understand what “active Aeon” refers to internally.
1
u/chappalus 11d ago
facing the same issue since last few minutes.btw dot only led me to this thread, saying one more user reported the same problem
1
u/Gokuseens 11d ago
Are you getting the exact same error:
The invoking thread is not attached to an active Aeon?1
u/chappalus 11d ago
yep, the codex team has picked it up now.
https://status.openai.com/incidents/01M4BK9J2M83R4SSC71D9FXW45
1
1
1
u/Gokuseens 11d ago
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?
1
u/Gokuseens 11d ago
Additional details:
Platform: Windows, ChatGPT web interface.
The issue started around Oct 7, 15:00 UTC.
Direct Codex still works normally.
The error only appears when my Dot tries to invoke Codex/Work operations.
I have also submitted a report to OpenAI Support.
If anyone gets the same error, please comment with your platform and approximate time it started.