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_proxy_needs_approval_retry

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.210, including the newest one read.

What it is

Retrying MCP calls that need approval now uses one shared rule, so behaviour is consistent.

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.210 – 2.1.243 33 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
v2.1.210 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.221MCP retroactive-approval retry check consolidated

    Retrying MCP calls that need approval now uses one shared rule, so behaviour is consistent.

    gate cited by this entry

  2. v2.1.210MCP Connector Approval Retry (CCR / -32003)

    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, up to twelve of them.

tengu_mcp_auto_backgroundNo description from anybody. 2.1.212 tengu_mcp_cgroupOn Linux you can force MCP servers into their own memory cgroup with an environment variable. never mined tengu_mcp_claudeai_eligibility_gateNo description from anybody. 2.1.212 tengu_mcp_cli_command_executedNo description from anybody. never mined tengu_mcp_connect_timeout_retryMCP connect timeouts now respect the global timeout and get retried instead of failing. 2.1.227 tengu_mcp_degradedMCP events are forwarded for logging with identifying fields stripped, and skipped entirely if analytics are off. never mined tengu_mcp_directory_bffNo description from anybody. 2.1.138 tengu_mcp_directory_visibilityNo description from anybody. 2.1.138 tengu_mcp_discovery_cacheThe /mcp view now counts cached servers separately so you can tell them from live connections. 2.1.221 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 tengu_mcp_drop_invalid_tool_schemasNo description from anybody. 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.