5 people reported

All time, since Oct 4, including 3 thumbs-up on GitHub.

Cloud workspace files lost

“During ongoing work, workers reported an execution disconnect followed by ENOENT for previously existing directories under /workspace/shared.”

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/10973/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

Cloud workspace files disappear during active work without a reset. Execution disconnects, then previously readable directories under /workspace/shared return ENOENT while reported filesystem usage drops sharply; no reset, replacement or deletion was requested.

Is this your bug?

File my report
Where
Dots cloud workspace
Error text
ENOENT
Platforms
Windows
How bad
Loses work: code or files lost or damaged.

Not quite your bug?

  1. Cloud environment fails capability query and cannot resume4 people
  2. Full cloud disk blocks sandbox startup and cleanup commands2 people
  3. Cloud Computer shows Unavailable7 people

Original reports2, newest first

  1. [Dots] Recent cloud-workspace files unavailable after execution stall; older files remain and filesystem identity changesOn GitHub#52765
  2. [Dots] Active cloud workspace files and test evidence became unavailable without a requested resetOn GitHub#50985

Do you work on Codex?

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