MCP servers restored from the discovery cache now report a proper 'pending' status instead of unknown.
tengu_mcp_discovery_cache 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.221: 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.
Read once, for one account on one subscription tier, against v2.1.221. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Servers whose tools came from the discovery cache now have a defined status in the serialized MCP server state used by the SDK and status consumers.
- The serializer exposing name, status, config, scope and serverInfo maps the internal
cachedclient type to the wire statuspending. serverInfois now reported for cached clients as well as connected ones.- Only reachable when the discovery cache actually produces a cached client, which is governed by
tengu_mcp_discovery_cache.
return e === "cached" ? "pending" : e;
Strings lifted out of the shipped bundle, so the claim above can be checked against them.