15 people reported

All time, since Oct 7, including 9 thumbs-up on GitHub.

Dot task coordination fails

“My existing dot conversation suddenly stopped being able to send instructions to Codex tasks or list connected computers.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/10554/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports and thumbs-up in the last two weeks, down from 16 a week at the early-October peak. A workaround is known.

Dot task coordination fails with active-Aeon error. An existing dot can no longer send messages to tasks or list environments, while chat and cloud_threads.read still work.

Is this your bug?

File my report
Where
Desktop app dot
Error text
RuntimeError: The invoking thread is not attached to an active Aeon
Versions
0.159.0 to 26.1002.52244
Platforms
macOS, Windows
How bad
Breaks a normal workflow. Some reports say it blocks them completely.

Part of: Dot can't access local threads12 bugs

  1. Dot cannot read local threads57 people
  2. Dot cloud task create and continue fail with UNKNOWN18 people
  3. list_threads/read_thread fail6 people
  4. codex_app MCP fails in dot tasks3 people
  5. Dot can't reach local threads7 people
  6. Existing thread read fails5 people
  7. Dot local task creation fails3 people
  8. Thread tools missing from tasks5 people
  9. Remote session read fails5 people
  10. Dots tasks missing browser tools5 people
Show all 11Show only the largest 10
  1. Dot tasks missing browser tools10 people

Not quite your bug?

  1. Task creation fails UNKNOWN3 people

Original reports6, newest first

  1. Dot cannot resolve active context: “The invoking thread is not attached to an active Aeon”On GitHub#51769
  2. Windows desktop 26.1002.52244: previously working dot task connection fails with “The invoking thread is not attached to an active Aeon”On GitHub#51757
  3. dot: environment discovery, task creation and child listing fail with active-Aeon errorOn GitHub#51746
  4. Dot task coordination fails: “The invoking thread is not attached to an active Aeon”On GitHub#51743
  5. Original active dot rejects environment discovery and task messaging: invoking thread is not attached to an active AeonOn GitHub#51742
  6. dot cannot create local tasks, reporting “not attached to an active Aeon”On GitHub#51730

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.