8 people reported
All time, since Oct 5, including 2 thumbs-up on GitHub.
Migrated Legacy Cloud environment cannot be edited or deleted
“After migrating an environment that I created in Legacy Codex Cloud, I can no longer edit it in the new Codex Cloud environment settings.”
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/10228/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
After migration the environment shows "Shared by me" or "Unpublished", Save changes is disabled with "Ask your admin for edit access".
Is this your bug?
File my report- Where
- Codex Cloud environments
- Error text
Ask your admin for edit access- Versions
- 26.1007.21159
- Platforms
- macOS, Windows
- How bad
- Breaks a normal workflow. Some reports say it blocks them completely.
Not quite your bug?
- Environment migration won't save6 people
- Legacy environment not editable13 people
- Environment publishing stuck2 people
Original reports6, newest first
- Codex Cloud – Environment incorrectly marked as shared, cannot edit or deleteOn GitHub#56427
- Codex Cloud: cannot edit my Legacy environment after migration (Windows web)On GitHub#53764
- macOS: Legacy Cloud migration leaves shared unpublished environments read-only; setup cannot finishOn GitHub#52901
- Migrated personal Codex Cloud environment becomes workspace-managed and cannot be edited or deletedOn GitHub#51982
- Migrated Legacy Codex Cloud environment becomes “Shared by me” and cannot be edited or deleted by its ownerOn GitHub#51695
- Can't delete stuck Codex EnvironmentOn GitHub#51109