{"version":"2.1.273","anchor":"bridge-server-config-gains-an-explicit-drop-auto-mode-envir","canonical_anchor":"bridge-server-config-gains-an-explicit-drop-auto-mode-envir","heading":"Bridge server-config gains an explicit 'drop auto mode environment' knob and user-configured tracking","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/bridge-server-config-gains-an-explicit-drop-auto-mode-envir","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Bridge server-config gains an explicit 'drop auto mode environment' knob and user-configured tracking\n\nBridge configuration can now explicitly drop the 'auto mode environment' setting, and tracks if you'd configured your own\n\n**Unclear.** What 'auto mode environment' configures in practice is still not explained by the evidence available.\n\n**What**\n\nWhen Claude Code applies configuration from a bridge server, it can now be told to explicitly strip out the `auto_mode_environment` setting from the incoming config via a new `dropAutoModeEnvironment` option. Separately, it now tracks and records whether you had already configured your own auto-mode environment before the bridge's config was applied.\n\n**Why**\n\nThis prevents a bridge server's configuration from silently overriding an auto-mode environment setting you'd already chosen yourself, and gives visibility into how often that situation happens.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}