{"version":"2.1.281","anchor":"sdkcli-managed-settings-payload-is-now-loaded-at-startup","canonical_anchor":"sdkcli-managed-settings-payload-is-now-loaded-at-startup","heading":"SDK\/CLI --managed-settings payload is now loaded at startup alongside --settings","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/sdkcli-managed-settings-payload-is-now-loaded-at-startup","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### SDK\/CLI --managed-settings payload is now loaded at startup alongside --settings\n\nThe `--managed-settings` payload, including the SDK's `managedSettings` option, is now actually loaded at startup\n\n**What**\n\nAt startup Claude Code reads settings passed on the command line. It used to load only the `--settings` flag. It now also loads the `--managed-settings` payload, and runs this step when either one is given.\n\nPrograms using the SDK, which lets code drive Claude Code, pass `Options.managedSettings`, which becomes `--managed-settings`.\n\n**Why**\n\nManaged settings passed this way now take effect in this startup path. Before, they were accepted but not applied there."}