What
Claude Code can connect to MCP (Model Context Protocol) servers, which requires building their connection configs. A new mechanism now caches that config-building work instead of redoing it every time, feeding into the existing MCP connection-management step.
This is controlled by a feature flag called the "artifact MCP switch" (tengu_cobalt_plinth_loquat). New per-session state tracks things like whether the switch has been decided (latched), whether MCP servers/entries have already been built, and how many entry-skips have been logged. The gate decision is made once per session and reported via telemetry. When the switch is off, the cache is a no-op and config building happens as before.
Why
The switch defaults to off, so this doesn't change current behavior yet, but it lays the groundwork to avoid rebuilding MCP server configs unnecessarily once enabled.
tengu_cobalt_plinth_loquat 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.265: off
Read once, for one account on one subscription tier, against v2.1.265. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_cobalt_plinth_loquat