claude-code - 💡(How to fix) Fix [BUG] Max plan: routine editor environment selector shows only "Default" with no settings icon and no "Add environment" option [1 comments, 2 participants]

Bug summary

On the routine editor at claude.ai/code/routines, the environment selector exposes only a "Default" entry with no way to edit it or create a new one. The UI affordances described in the docs do not render.

Observed

Opening a routine and clicking the environment selector (labeled "Default" with a cloud icon) opens a dropdown panel containing exactly two things:

1. A search field with placeholder text "Environment"
2. A single entry labeled "Default"

That is the entire contents of the panel. No "Add environment" button, no "+ New" affordance, and no settings/gear icon next to the "Default" entry — neither statically rendered nor on hover. There are no other controls or scroll affordances.

This contradicts two statements in the docs:

• "Add an environment: Select the current environment to open the selector, then select Add environment." — there is no "Add environment" control in the selector.
• "Edit an environment: Select the settings icon to the right of the environment name." — no settings icon appears next to "Default".

Impact

Without access to the environment editor, there is no self-serve way to modify the network egress allowlist, change environment variables, or configure a setup script for a routine. In particular this blocks any routine that needs outbound HTTP to a non-default host (SEC EDGAR, Yahoo Finance, Slack API, etc.), which is the scenario already reported in #50146, #30112, and #19087.

Relevant difference from those issues: they're about the allowlist contents or propagation; this issue is about the UI affordance being absent entirely — i.e. even if the allowlist mechanism worked, a Max user has no way to reach it.

Setup

• Plan: Max
• Browser: Chrome (latest, on macOS)
• Account: solo (no workspace/org)

Expected

Either:

1. The "Add environment" option and the settings icon next to each environment entry should render as documented — or
2. The docs should state that environment customization requires a specific plan tier (Team/Enterprise) or feature-flag, and direct Max users to an alternative.

Happy to provide account UUID or other diagnostic info privately if useful.