Dot cloud computer unavailable since October 29: root executor preparation fails

ChatGPT Dots
1

My dot’s built-in cloud computer became unavailable on October 29, 2026 (my local EDT date) and is still unavailable on October 30. The exact onset time is unknown; the October 30 diagnostic timestamps linked below are later checks, not the start of the incident.

Dot chat and connected services still work, and a separately connected local computer can run tasks. The built-in cloud computer remains disconnected/unavailable. Pausing and unpausing did not restore it. I have observed this from Windows web and iOS; exact builds are unknown.

Repeated startup errors (environment identifier omitted):

  • exec-server connection attempt failed: environment unavailable: Root executor preparation for your dot failed
  • failed to query executor configuration capabilities for environment
  • Even a minimal command returns: No usable execution environment is available. Wait for an environment to become available before using this tool.

I submitted in-app feedback/support and recorded the diagnostic timestamps in this public GitHub report: Dots cloud computer failed: “Root executor preparation for your dot failed” / env unavailable (Windows desktop) · Issue #50545 · openai/codex · GitHub

No data loss or shared root cause is confirmed. Is there a supported, non-destructive recovery path that preserves the existing workspace?

2

Since October 29, my Dot has been unable to use its cloud computer due to repeated root executor preparation failures.

As of today, October 31, the behavior has changed. My Dot is now responding with the following message:

Your dot is on a break. Congrats you are in the very top users and have hit our abuse prevention limit. Check back in a bit!

This is particularly concerning because it suggests my account or Dot has now been subjected to an abuse prevention limit, despite my usage consisting of legitimate research and project workflows.

I’d appreciate clarification on a few things:

  1. Is this abuse prevention limit related to the cloud computer failures I’ve been experiencing since October 29, or is it a separate issue?

  2. What specifically triggers this limit, and is it based on usage volume, execution frequency, or another metric?

  3. Is this a temporary cooldown, and if so, when can I expect access to be restored?

  4. Could the repeated failed executor preparation attempts have contributed to triggering the limit?

  5. Is there an account-level restriction currently affecting my Dot, and can it be reviewed?

I’ve been using Dot extensively for ongoing research and project management, and these interruptions have effectively prevented me from using the functionality as intended.

I would appreciate a technical explanation of what is happening rather than another generic recommendation to check back later.