{"version":"2.1.281","anchor":"managed-settings-is-carried-through-to-spawned-sessions","canonical_anchor":"managed-settings-is-carried-through-to-spawned-sessions","heading":"--managed-settings is carried through to spawned sessions; --setting-sources is accepted and discarded by one argument parser","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/managed-settings-is-carried-through-to-spawned-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### `--managed-settings` is carried through to spawned sessions; `--setting-sources` is accepted and discarded by one argument parser\n\n--managed-settings is now passed on to sessions Claude Code starts itself, while one parser reads --setting-sources and throws the value away\n\n**Unclear.** The finding does not say whether a `--setting-sources` value still reaches spawned sessions through the separately stored field.\n\n**What**\n\nClaude Code has an early argument reader that handles the `agents` command and the arguments for its background process (a daemon). That reader now picks up `--managed-settings <value>`. It passes the value on as `--managed-settings` to sessions it starts itself, together with `--settings`, `--plugin-dir`, `--add-dir` and the other flags it already passes on.\n\nThe same reader also accepts `--setting-sources` but does nothing with its value. A separate part that rebuilds the argument list can still output `--setting-sources=` from a value stored elsewhere.\n\n**Why**\n\nIf you start Claude Code with `--managed-settings`, the sessions it starts on your behalf now receive the same value. For `--setting-sources`, this particular reader no longer carries your value forward."}