Codex cloud executor dead after file-transfer timeout; reboot requests fail silently with no logs
COOLak · ghdev · 2026-10-09
Issue #52509 in openai/codex tracks a [Dots] cloud executor that stops responding and can't resume after a file-transfer timeout; a fresh diagnostic pass remains unresolved.
- Minimal pwd probes at 15:44–16:01 UTC were rejected with No usable execution environment is available; cloud startup failed querying executor configuration capabilities.
- Local side verified healthy: a separate task on the connected Windows machine ran PowerShell and read the desktop app version 26.1002.7124.0.
- The desktop Reboot handler sends POST /cloud-aeons/primary/reboot with retries disabled and bypasses the normal saserverrequestfailed logging wrapper — six desktop logs showed no HTTP status, response body or request ID.
- Some attempts showed "Reboot requested" without restoring execution; request acceptance does not imply recovery.
More from coding & agent
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23
- How do you audit AI agent decisions in regulated workflows? A field survey — Ok_Way_1993 · 2026-10-23