Rank, 14 days: 71 on the Codex sheet
6 people reported
All time, since Oct 16, including 5 thumbs-up on GitHub.
Cloud environment stuck offline
“My existing Codex Cloud environment is stuck in an offline state, and I can no longer access its workspace.”
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/18627/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 environment stuck offline, workspace with uncommitted changes inaccessible. Environment reports connectivity: offline, commands like git status --short cannot run, and publishing environment settings fails with the save-confirmation message.
Is this your bug?
File my report- Where
- Codex Cloud environment
- Error text
Unable to confirm that your settings were saved.- How bad
- Loses work: code or files lost or damaged.
Not quite your bug?
Original reports1, newest first
- Codex Cloud environment stuck offline — cannot access workspace with uncommitted changesOn GitHub#54666