{"version":"2.1.296","anchor":"settings-payloads-gain-an-undercode-scope","canonical_anchor":"settings-payloads-gain-an-undercode-scope","heading":"Managed settings gain an underCode option for desktop sessions","tier":"internal","area":"Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/settings-payloads-gain-an-undercode-scope","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Managed settings gain an underCode option for desktop sessions\n\nManaged settings entries can now set underCode, which builds the desktop session's settings from the CLI settings without needing serve_to_desktop\n\n**What**\n\nManaged settings are settings an organization pushes out to Claude Code. Each entry in them now carries an `underCode` field.\n\n- When `underCode` is true, the settings handed to the desktop app's sessions (`desktopSessionPayload`) are built from a transformed copy of the CLI settings. The copy is produced by an internal helper (`yut`).\n\n- Otherwise the old rule still applies. The desktop payload is only sent when `serve_to_desktop` is true and the settings are not empty.\n\n**Why**\n\nIn practice, an entry can now reach desktop sessions without being marked `serve_to_desktop`. Administrators who manage settings for desktop users have a second way to deliver them.\n\n- Area: Gateway\n- Names: `underCode`, `serve_to_desktop`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}