tengu_mcp_listen_reopen
A Claude Code feature flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
MCP notification streams now reconnect after a server drop or redeploy instead of silently going dead.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.221.
In the changelogs
4Releases whose published page names tengu_mcp_listen_reopen.
-
v2.1.233
MCP event subscriptions back off instead of reconnecting in a tight loop
A flaky MCP server that keeps dropping event streams now gets a pause instead of endless instant reconnects.
gate cited by this entry, found in this entry's text
-
v2.1.224
MCP telemetry identifies servers by a hash, not the base URL
MCP telemetry identifies servers by a hash rather than their raw URL.
gate cited by this entry, found in this entry's text
-
v2.1.224
MCP events forwarded to Datadog, with identifying fields removed and a per-server cap
MCP events are forwarded for logging with identifying fields stripped, and skipped entirely if analytics are off.
gate cited by this entry, found in this entry's text
-
v2.1.221
MCP subscriptions/listen streams are re-opened after drops
MCP notification streams now reconnect after a server drop or redeploy instead of silently going dead.
gate cited by this entry, found in this entry's text
Gate readings
0No release here has a gate table behind it for this flag. Most published releases have none at all: the readings exist only for versions the pipeline captured flag state on.
First cited
1The earliest release whose published evidence quoted tengu_mcp_listen_reopen was v2.1.248, 27 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was 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.