{"version":"2.1.323","anchor":"new-managed-settings-in-initialize-flag-incompatible-with","canonical_anchor":"new-managed-settings-in-initialize-flag-incompatible-with","heading":"New --managed-settings-in-initialize flag, not allowed with background modes","tier":"use","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/new-managed-settings-in-initialize-flag-incompatible-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### New --managed-settings-in-initialize flag, not allowed with background modes\n\nClaude Code has a new `--managed-settings-in-initialize` flag, which refuses to run alongside `--bg`, `--background`, `--routine` or `--tmux`\n\n**What**\n\nA flag is an option you add when starting a command. Claude Code has a new one, `--managed-settings-in-initialize`. It cannot be used together with any of these, and Claude Code stops with an error if you try:\n\n- `--bg` or `--background`\n\n- `--routine`\n\n- `--tmux`\n\n- a background session command\n\nThere is also a new faster route for `claude plugin validate --module`.\n\n**Why**\n\nIt gives programs that build on Claude Code through the SDK a way to supply managed settings (settings an organization sets centrally) when the session starts, rather than from files on disk.\n\n- Area: Managed Settings\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}