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

All time, since Oct 23.

Cloud environment stuck starting

“Não consigo publicar nem utilizar meu ambiente na nuvem chamado “vsl”.”

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/21324/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 starting; publish fails and commands cannot run. Environment shows connected but phase stays starting with empty capabilities; publishing reports settings saved but the environment could not be published, persisting after app restart.

Is this your bug?

File my report
Where
Cloud environment
Error text
failed to query executor configuration capabilities
Platforms
macOS, Windows
How bad
Stops work: a core feature can't be used.

Not quite your bug?

  1. Cloud environment fails capability query and cannot resume4 people
  2. Cloud environment stuck starting4 people
  3. Cloud environment publish fails5 people

Original reports2, newest first

  1. macOS: cloud environment stays connected/starting; publication fails and commands cannot executeOn GitHub#56926
  2. Cloud environment will neither publish nor start, preventing access to filesOn GitHub#56473

Do you work on Codex?

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