{"version":"2.1.269","anchor":"new-bridge-server-config-telemetry-for-auto-mode-environment","canonical_anchor":"new-automodesettingsjson-passed-to-spawned-cli-sessions-when","heading":"New 'auto mode environment' setting carried through bridge\/cloud sessions","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-bridge-server-config-telemetry-for-auto-mode-environment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New 'auto mode environment' setting carried through bridge\/cloud sessions\n\nSessions can now carry an auto_mode_environment description from the dispatching service into context, config, and telemetry\n\n**Unclear.** The finding doesn't say what auto_mode_environment itself represents or controls.\n\n**What**\n\n- A new optional `auto_mode_environment` field was added: a config schema field, a matching `autoModeEnvironment: []` default in session state, and support for it in the bridge\/cloud session-launch path.\n\n- Sessions launched via the bridge\/cloud path can receive an `auto_mode_environment` array of strings from the dispatching service; each entry is validated (length caps, no control\/invisible characters) and injected into the session's context as \"Stated by the service that dispatched this session ...\" lines.\n\n- When spawning a CLI session, Claude Code now also computes `autoModeSettingsJson` from any configured `autoModeEnvironment` list and includes it in the launch config alongside `mcpConfig`\/`appendSystemPrompt`.\n\n- When spawning a worker for a remote-control (bridge) session whose work item carries `auto_mode_environment`, Claude Code re-checks the local `userSettings`\/`policySettings` auto-mode environment config and passes a computed `userAutoModeEnvironmentConfigured` flag into the session-spawn call.\n\n- New telemetry was added: bridge server-config apply\/rejected events now include an `auto_mode_environment` count and a `carried_auto_mode_environment` flag, plus a new debug reason, `auto_mode_environment_dropped`, that fires when the value was carried but ended up empty after filtering.\n\n**Why** This lets a service that dispatches automated (\"auto mode\") sessions describe the environment it's running in, so that description can be surfaced to the model as context and tracked through config and telemetry.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}