Rank, 14 days: 123 on the Codex sheet
2 people reported

All time, since Oct 31.

Cloud task loses workspace

“An existing bounded background computation in a Cloud task has previously lost its accessible worker processes after the accessible runtime identity changed.”

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

Running Cloud task loses its working directory and executor. The existing working directory could not be found while the environment reported "connected / running"; a checkpoint stayed readable but later completed work was not found.

Is this your bug?

File my report
Where
Codex Cloud tasks
Versions
0.166.0
Platforms
macOS, 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. Published environment not applied3 people
  3. Managed cloud thread rejects messages6 people

Original reports2, newest first

  1. [Codex Cloud] Active task loses executor and working directory around environment republishOn GitHub#59567
  2. Cloud task intermittently lacks its existing workspace; supported runtime reattachment is unclearOn GitHub#58611

Do you work on Codex?

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