Unclear What triggers the extra MCP configuration and allowed-tools merge is not clear.
The order of steps when Claude Code starts has changed:
- When Claude Code is not running headless (headless means without its interactive screen, for example from a script), one startup path now merges in an extra MCP configuration and list of allowed tools. MCP servers are add-ons that give Claude Code extra tools.
- Interactive startup now waits for MCP servers that had been held back before carrying on.
- After onboarding, Claude Code records how long its remote feature-setting system took to start.
Startup behaves differently, so the moment MCP tools become available in an interactive session may shift.
tengu_mcp_startup_policy_seed Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.290: on
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.
tengu_cicada_nap_ms Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.290: not a boolean we can read
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.
Read once, for one account on one subscription tier, against v2.1.290. It isn't a statement about your account. What a flag value here can and cannot tell you
What triggers the extra MCP configuration and allowed-tools merge is not clear.