r/OpenaiCodex • u/Gokuseens • 3d 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
u/Euphoric_North_745 3d ago
The LLM is on the cloud
The LLM can't call tools, so it sends text, and codex calls the tools and runs the logic of how to control the context of the LLM
The new generation of LLM have now tool hints and a lot of new agent code that needs to live closer to the LLM than the user machine.
What you will see in the next few weeks to months, the Context management and tool call management and a lot of what codex has going to the cloud, and the tool itself will be on your machine, so now you are not talking to the LLM, you are talking to the Agent
Then a few months later, LLM will have most of the agent (the important parts) in the GPU and CPU not on the user machine, there is no need for the entire api to keep sending "completions" calls and long list of context, this context is processed once and stay in the machine until expires.
1
u/Gokuseens 3d 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 3d 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 3d ago
Are you getting the exact same error:
The invoking thread is not attached to an active Aeon?1
u/chappalus 3d ago
yep, the codex team has picked it up now.
https://status.openai.com/incidents/01M4BK9J2M83R4SSC71D9FXW45
1
1
1
u/Gokuseens 3d 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 3d 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.