{"version":"2.1.318","anchor":"startup-command-scan-tied-to-mcp-config-behind-tengu-amber","canonical_anchor":"startup-command-scan-tied-to-mcp-config-behind-tengu-amber","heading":"A start-up command scan can wait for MCP settings to load","tier":"soon","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/startup-command-scan-tied-to-mcp-config-behind-tengu-amber","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### A start-up command scan can wait for MCP settings to load\n\nBehind a remote switch that is off by default, Claude Code can run a start-up command scan only after MCP settings finish loading\n\n**Unclear.** What the start-up command scan does is not shown.\n\n**What**\n\nClaude Code can now run a command scan during start-up after it has finished loading your MCP settings. MCP servers are outside programs that give Claude extra tools. This sits behind a remote switch that is off unless it is switched on remotely.\n\n**Why**\n\nIt changes the order of start-up steps, so the scan runs once MCP settings are known.\n\n- Flag `tengu_amber_sluice`: Not enough to say (read for one account on one subscription tier against v2.1.318; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}