{"version":"2.1.323","anchor":"sdk-managedsettingsviainitialize","canonical_anchor":"sdk-managedsettingsviainitialize","heading":"SDK can pass 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-managedsettingsviainitialize","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### SDK can pass managed settings at startup instead of on the command line\n\nA new SDK option, `managedSettingsViaInitialize`, stops managed settings from being passed as a command-line argument\n\n**Unclear.** It is not clear what turns this option on, or whether developers can set it themselves.\n\n**What**\n\nThe SDK is a toolkit for running Claude Code from other software. It has a new option, `managedSettingsViaInitialize`. Managed settings are settings an organization sets for its users. When this option is set, the SDK no longer passes managed settings to Claude Code as a command-line argument.\n\n**Why**\n\nManaged settings are sent in the first message the SDK exchanges with Claude Code when it starts, instead of being written into the command that launches it.\n\n- Area: SDK\n- Names: `managedSettingsViaInitialize`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}