What
MCP servers are add-ons that give Claude extra tools. In a remote session, Claude Code works in a workspace on another machine. MCP runs in that remote workspace, so servers you set up on your own machine are not used. The warning about this changed:
- It says that servers from
--mcp-configor from agent frontmatter are ignored because "MCP runs in the remote workspace". Agent frontmatter is the settings block at the top of an agent file. - It also warns that
--chrome, the option for Chrome browser integration, has no effect in that case. - One helper now builds the warning from
mcpConfigFlagServers, the agent, the chrome flag anddynamicMcpConfig. Before, the warning was built inline for every dynamic MCP server and only mentioned--mcp-configand agent frontmatter.
Why
If you pass --mcp-config or --chrome to a remote session, you now get a warning that these options do nothing there. The wording of the warning, and which servers it lists, may differ from before.
Names in the bundle--chrome
--chrome
Continue local sessions from any device with Remote Control modified, high confidence
> | `--chrome` / `--no-chrome` | Turn [Chrome integration](https://code.claude.com/docs/en/chrome.md) on or off in the sessions the server creates, so Claude can use Chrome on your machine while you work from another device. Without either…see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
--chrome on Continue local sessions from any device with Remote Control