What
claude agents opens the fleet view of your agents. It now respects these flags:
--settings, a settings file or inline settings for this session--managed-settings--setting-sources, which chooses which kinds of settings to load
The startup step that reads the agents command now recognises --managed-settings. It passes that flag on, along with --setting-sources=<value> when one is set.
Why
The fleet view now uses the same settings as the rest of your session instead of ignoring these flags.
Names in the bundleclaude agents--settings
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude agents, on Set up Claude Code for your organization.
| [Disable agent view](/docs/en/agent-view#how-background-sessions-are-hosted) | Turn off `claude agents`, `--bg`, `/background`, and the on-demand supervisor | `disableAgentView` |admin-setup see the edit
Confirmed since
Anthropic's documentation has since written up --settings, on Claude Code changelog.
* Changed `sandbox.excludedCommands` to ignore project and local settings entries when managed settings or `--settings` set `allowUnsandboxedCommands: false`, or managed `allowManagedDomainsOnly: true`changelog see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up --settings, on Claude Code changelog.
Anthropic's release notes agree
Fixed --setting-sources (and SDK settingSources) not being forwarded to spawned sessions: teammates, /bg, claude agents sessions and…