[BUG] "Cannot edit existing cloud environment from web UI

Resolved 💬 4 comments Opened Apr 24, 2026 by Francois3d Closed Apr 24, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Between Apr 23 and Apr 24, 2026, the cloud environment management UI in claude.ai/code broke. Specifically:

Edit existing environment: the docs say to "Select the settings icon to the right of the environment name" in the env selector dropdown (per https://code.claude.com/docs/en/claude-code-on-the-web#configure-your-environment). The settings icon is no longer present, even on hover. Yesterday it was there.
"+ Add environment" option: docs say "Select the current environment to open the selector, then select Add environment." That option is no longer in the dropdown.
Net effect: I have a valid existing environment (env_019GaXrqkhScFD7x5dArZygi) but cannot update its env variables (need to rotate a password), and cannot create a new environment as a workaround.

CLI status: /remote-env works but per docs only handles selection of default, not editing. So no CLI workaround is documented either.

What Should Happen?

i should be able to edit the environment in the routine or add a new environment

Error Messages/Logs

No error messages.

Steps to Reproduce

Open the Claude code on the desktop or the web.
Click routines,
edit the existing cloud routine by clicking the pencil
in the instructions' bottom right. The environment normally has a default.
Click on default - environments should be listed.

cannot add or edit existing environment variables.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.104

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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