{"version":"2.1.281","anchor":"hidden-managed-settings-flag-added-to-claude-agents-and","canonical_anchor":"hidden-managed-settings-flag-added-to-claude-agents-and","heading":"Hidden --managed-settings flag added to claude agents and forwarded to dispatched sessions","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/hidden-managed-settings-flag-added-to-claude-agents-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Hidden --managed-settings flag added to `claude agents` and forwarded to dispatched sessions\n\n`claude agents` gains a hidden `--managed-settings ` option that is passed on to sessions it starts\n\n**What**\n\nThe `claude agents` command now accepts a hidden `--managed-settings <json>` option. A hidden option works but is not listed in the help text. It means the same as the main command's option of that name, described as \"Policy-tier settings JSON from a spawning parent process (SDK use only)\". Policy-tier settings are the organisation-level settings that sit above a user's own.\n\nThe option now also joins `--settings`, `--mcp-config` and `--setting-sources` in the group of flags that are handed on to sessions `claude agents` starts.\n\n**Why**\n\nA program that launches Claude Code through the SDK (the kit for driving Claude Code from other software) can now give `claude agents` policy settings and have them reach the sessions it starts. It is marked for SDK use only and is not something to type by hand."}