{"version":"2.1.281","anchor":"mcp-policy-cold-start-now-also-waits-for-remote-managed-sett","canonical_anchor":"mcp-policy-cold-start-now-also-waits-for-remote-managed-sett","heading":"MCP policy cold start now also waits for remote managed settings in non-interactive sessions","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/mcp-policy-cold-start-now-also-waits-for-remote-managed-sett","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### MCP policy cold start now also waits for remote managed settings in non-interactive sessions\n\nNon-interactive sessions now wait for remote managed settings to load before connecting MCP servers\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Managed settings are settings an organization sets centrally, and some are loaded remotely. At startup, Claude Code could already wait for those remote managed settings before connecting MCP servers. A new condition now triggers that wait as well: sessions that are not interactive, such as headless or print-mode runs where no one is typing at a prompt.\n\n**Why**\n\nIn scripted and automated runs, MCP servers now connect only after the organization's remote settings are in place, so those settings apply from the start."}