{"version":"2.1.281","anchor":"teammate-spawn-commands-carry-managed-settings-mcp-conf","canonical_anchor":"teammate-spawn-commands-carry-managed-settings-mcp-conf","heading":"Teammate spawn commands carry --managed-settings, --mcp-config and --strict-mcp-config","tier":"notice","area":"Agents","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/teammate-spawn-commands-carry-managed-settings-mcp-conf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Teammate spawn commands carry --managed-settings, --mcp-config and --strict-mcp-config\n\nSpawned teammates and agents now inherit --managed-settings, --mcp-config and --strict-mcp-config from the launching command\n\n**What**\n\nClaude Code can start helper instances, called teammates or agents, that work alongside the main one. The command it builds to start them now passes along these options from your own command line:\n\n- `--managed-settings`, rewritten as normalized JSON, or `\"invalid\"` if it could not be read\n\n- every `--mcp-config`, with inline JSON rewritten in a standard form\n\n- `--strict-mcp-config`\n\nTeammates opened in tmux windows (a tool that splits one terminal into several) also receive an extra argument carrying environment and options.\n\n**Why**\n\nHelpers now start with the same MCP servers (outside tools and data sources Claude can connect to) and the same managed settings as the session that launched them. If you use `--strict-mcp-config` to allow only certain servers, that limit now applies to helpers too.\n\n- Area: Agents\n- Names: `--mcp-config`, `--strict-mcp-config`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}