Source Intelligence
Follow Discord
Sweep 28 Aug 2026 · 00:00Z Build v2.1.250 478 read Stable v2.1.236 Latest v2.1.250 Next v2.1.250 Feeds RSS JSON llms.txt

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

Reference / Feature flags

tengu_mcp_discovery_cache

A Claude Code feature flag, read out of the shipped bundle. It was in the build from v2.1.221 and was gone by v2.1.238.

What it is

The /mcp view now counts cached servers separately so you can tell them from live connections.

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.221.

Presence across releases

ReleasesReadingDeclared typeDefault
2.1.245 – 2.1.250 5 releases never mined — —
2.1.238 – 2.1.243 6 releases not in the build — —
2.1.221 – 2.1.237 16 releases in the build — bool:true

A row reading never mined is a release with no archived bundle behind it. Nothing was read out of it, so nothing here says whether the name was in it. A declared type or a default is only ever what that release's own bundle stated.

Gate readings

ReleaseResolvedThis accountAnonymousCompiled default
v2.1.221 read on another version Not enough to say no value returned no value returned off

Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.

Changelog entries naming it

  1. v2.1.221/mcp status surfaces cached servers

    The /mcp view now counts cached servers separately so you can tell them from live connections.

    gate cited by this entry

  2. v2.1.221MCP servers can start from a discovery cache and connect lazily

    Startup no longer dials cached HTTP or SSE MCP servers; they restore from cache and connect on first use.

    gate cited by this entry

  3. v2.1.221MCP servers can start in a new "cached" state instead of blocking on connect

    MCP servers with a saved cache now show tools instantly and only connect when you first use them.

    gate cited by this entry

  4. v2.1.221Discovery-cache misses are classified in telemetry

    MCP tool discovery now logs whether the cache was used, and servers with skills or channels deliberately skip it.

    gate cited by this entry

  5. v2.1.221MCP task restore dials lazily-cached servers instead of giving up

    Resuming a long-running MCP task after a restart now reconnects cached servers instead of failing.

    gate cited by this entry

  6. v2.1.221Cache-backed MCP servers report as pending rather than unknown

    MCP servers restored from the discovery cache now report a proper 'pending' status instead of unknown.

    gate cited by this entry

Documentation pages

None of Anthropic's documentation pages this site has a copy of carries this name.

Names beside it

Every feature flag in the inventory starting tengu_mcp_discovery, up to twelve of them.

tengu_mcp_discovery_cache_enableCalling a tool on a disabled MCP server would tell you to re-enable it, but that path is off. 2.1.238 tengu_mcp_discovery_sourceStartup no longer dials cached HTTP or SSE MCP servers; they restore from cache and connect on first use. never mined

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.