{"version":"2.1.273","anchor":"new-remote-control-cli-flags-chrome-no-chrome","canonical_anchor":"new-chrome-flag-for-spawned-sessions","heading":"New --chrome flag for spawned and remote-control sessions","tier":"use","area":"Chrome","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-remote-control-cli-flags-chrome-no-chrome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New --chrome flag for spawned and remote-control sessions\n\nA new --chrome \/ --no-chrome flag controls whether spawned and Remote Control sessions can use Claude in Chrome\n\n**What**\n\n- Spawning or reattaching a session now supports a `--[no-]chrome` flag that controls whether \"Claude in Chrome\" is available for that session, defaulting to the machine's own Chrome setting.\n\n- The `claude remote-control` command's argument parser also gained matching `--chrome`\/`--no-chrome` flags.\n\n- When Remote Control starts with `--chrome`, Claude Code now checks whether an enterprise MCP policy or a denied-MCP-servers list blocks the Claude-in-Chrome MCP server, and exits with an error instead of silently proceeding if it's blocked.\n\n- Child sessions spawned by Remote Control now inherit the `--chrome` setting from their parent, so the option is passed through consistently.\n\n**Why**\n\nThis gives explicit, per-session control over whether Claude in Chrome is enabled, and ensures that enterprise policies restricting MCP servers (which Claude in Chrome relies on) are respected rather than bypassed when Remote Control starts with Chrome access requested.\n\n- Area: Chrome\n- Names: `--chrome`, `--no-chrome`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}