{"version":"2.1.323","anchor":"sdk-managedsettingsdelivery-option","canonical_anchor":"sdk-managedsettingsdelivery-option","heading":"SDK can send managed settings at startup instead of on the command line","tier":"use","area":"SDK","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/sdk-managedsettingsdelivery-option","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### SDK can send managed settings at startup instead of on the command line\n\nA new SDK option, managedSettingsDelivery, lets managed settings be sent with the startup request and ends the session if they are not confirmed\n\n**What**\n\nThe SDK, the toolkit programs use to run Claude Code, has a new option, `managedSettingsDelivery`. Managed settings are settings an organization enforces centrally. The option takes one of two values:\n\n- `'argv'`, the default, passes the managed settings on the command line when Claude Code starts.\n\n- `'initialize'` sends them in the first request the SDK makes to start the session.\n\nWith `'initialize'`, if Claude Code does not confirm that it applied the managed settings, the session is ended. Any other value is rejected as invalid. A matching option, `managedSettingsInInitialize`, also appears among the options for print mode.\n\n**Why**\n\nPrograms built on the SDK can now deliver managed settings through the startup request. Because the session ends when they are not confirmed, a session never runs without them by accident.\n\n- Area: SDK\n- Names: `managedSettingsDelivery`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}