[BUG] Update cloud environment: "Failed to update environment. You can try again." — Save always fails for both Full-access preset and Custom allowlist

Status Open

Maintainer reply None cached

Activity 2 comments · opened Aug 8, 2026

Environment

Claude Code on the web (claude.ai/code)
Cloud environment (name: ccr-plugin-default)
Currently has one active session running against the environment
Session started 2026-08-08

Bug

The Update cloud environment dialog (Environments → edit) fails to save any change with the generic banner:

⚠️ Failed to update environment. You can try again.

No further error details are surfaced in the UI. The failure is deterministic across at least two distinct kinds of changes:

Changing Network access from the current preset to Full, no other edits, then Save changes → fails.
Changing Network access to Custom and adding two Allowed domains (github.com, results-receiver.actions.githubusercontent.com), then Save changes → fails.

Retrying the same save immediately (as the banner suggests) does not help — it fails every attempt.

What I was trying to do

Whitelist the hosts GitHub Actions redirects to for CI log downloads (results-receiver.actions.githubusercontent.com and Azure blob storage), so a Claude Code session can read failing CI logs directly via curl instead of only reasoning from step names.

Expected

Save succeeds; the change takes effect on new sessions (the dialog explicitly says "Changes to your environment will apply to new sessions").

Diagnostics I couldn't do from inside the running session

No HTTP status code / error id shown in the UI to correlate with a server log.
No indication whether the failure is because the environment is bound to a currently-running session (would explain why "changes apply to new sessions" is displayed) — if that IS the reason, the UI should surface it explicitly instead of a generic "try again" message.

Suggested fix / UX ask

Either:

Allow the save while a session is running (the change would apply to new sessions anyway per the existing dialog copy), OR
Explicitly block the save with a helpful message like "Close active sessions in this environment before editing."

Right now the failure is opaque: user can't tell whether it's a transient backend error, a validation error, or a session-in-use conflict.

#30112 covers the runtime behavior of the Cowork egress allowlist (blocking configured domains), which is a separate issue from the config UI being unable to save changes.

Screenshots

Happy to attach — please add if useful; the two Save attempts (Full preset and Custom allowlist) both surface the same banner.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗