You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
New FeaturesKind: in v2.1.229,
New FeaturesSection of the release
What
When a session runs in remote mode and an enterprise-managed MCP config file (managed-mcp.json) is present, MCP servers from every other source are dropped, each with a per-server explanation. Servers passed with --mcp-config get a matching warning instead of silently disappearing.
Details
Requires the CLAUDE_CODE_REMOTE environment variable plus the presence of an enterprise managed-mcp.json.
Joins the existing hermetic-mode drop path; the shared drop helper gained a branch reporting the reason as "enterprise MCP config".
Evidence
Ignored: an enterprise MCP config (managed-mcp.json) is present and has exclusive control over MCP servers
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up --mcp-config, on CLI reference.| `claude agents` | Open [agent view](/docs/en/agent-view) to monitor and dispatch parallel background sessions. Use `--cwd <path>` to show only sessions started under that directory, or `--json` to print active sessions as a JSON array fo…cli-referencesee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --mcp-config, on CLI reference.
Anthropic's release notes agreeFixed self-hosted runner and other remote sessions exiting at startup when managed-mcp.json is deployed and the server delivers MCP servers…
