Source Intelligence

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.

All of v2.1.217 Home All releases olderv2.1.216 v2.1.218newer
Claude Code v2.1.217

tengu_moth_copse — Voice/MCP URL Elicitation Toggle [Feature-Flagged]

Feature flag
tengu_moth_copse Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.217: on

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.217. It isn't a statement about your account. What a flag value here can and cannot tell you

What

A feature flag tengu_moth_copse controls whether the MCP URL elicitation flow (asking users to provide a URL for MCP server connection) is active. When the flag is on, a separate function rVi() is also checked.

Status

Feature-flagged (tengu_moth_copse)

Details
  • The gated function POe() returns true if either tengu_moth_copse is set or rVi() returns true; rVi() returns true when the CLAUDE_MEMORY_STORES env var is non-empty or the internal discovery latch YXn has fired (set by nVi(), which emits the v6c event when an external store announces itself)
  • When POe() is true, AutoMem-type local auto-memory entries are suppressed in two places: uso() filters them from context arrays and YAu() returns false for them, preventing local CLAUDE.md auto-memory from appearing in the model context alongside externally-discovered stores
  • Auto-memory prompt variant injection (prompt_variant: "base") is suppressed when POe() is true, removing local-index writing instructions from the system prompt
  • Full local memory-index content injection in I$u() is disabled when POe() is true (the s path is only taken when !POe())
  • The per-turn memory selector oHs() — which routes memory writes to the appropriate registered external store — only activates when both Em() (auto-memory globally on) and POe() are true; without POe(), the selector never runs even when auto-memory is otherwise active
Evidence

POe() function (search for "tengu_moth_copse" inside it), AutoMem suppression callers (search for "e.type === \"AutoMem\" && POe()" in YAu() and "filter((t) => t.type !== \"AutoMem\"" in uso()), memory selector guard (search for "!n || t.agentId || !Em() || !POe()" in oHs())

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.217 →