tengu_mcp_legacy_url_elicitation
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.281, including the newest one read.
MCP server configs accept a new bareElicitationCapability option that gives the server the plain elicitation capability instead of the legacy URL one
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.281.
In the changelogs
8Releases whose published page names tengu_mcp_legacy_url_elicitation.
-
v2.1.287
Setting
alwaysLoadto false on an MCP server now holds back all of its toolsAn MCP server configured with
alwaysLoadset to false is now marked as holding back every one of its toolsgate cited by this entry
-
v2.1.287
MCP servers on common connection types now get link and form requests by default
Claude Code now defaults to offering link and form input requests to MCP servers on stdio, sse, http or ws connections
gate cited by this entry
-
v2.1.287
A server-controlled MCP switch now defaults to on
The built-in default of one server-controlled MCP switch changed from off to on, with no linked change in behaviour found
gate cited by this entry, found in this entry's text
-
v2.1.287
MCP servers over HTTP get handling for older URL-based input requests
Connecting to an MCP server over HTTP can now wrap its requests for older URL-based input requests, and that path now falls back to on
gate cited by this entry, found in this entry's text
-
v2.1.287
Hook output no longer has a blank line above it
The display of hook output drops the one-line gap that used to sit above it
gate cited by this entry
-
v2.1.281
New
bareElicitationCapabilityMCP server optionMCP server configs accept a new
bareElicitationCapabilityoption that gives the server the plain elicitation capability instead of the legacy URL onegate cited by this entry
-
v2.1.281
New MCP server config key
bareElicitationCapabilityonly matters behind legacy elicitation gate (fallback off)MCP server configs accept
bareElicitationCapability, which only has an effect behind thetengu_mcp_legacy_url_elicitationgategate cited by this entry, found in this entry's text
-
v2.1.281
Legacy URL-elicitation capability advertised to MCP servers, with a per-server denylist (gated off)
Claude Code can tell MCP servers it supports URL and form requests for input, behind a flag whose fallback is false and a per-server denylist
gate cited by this entry, found in this entry's text
Gate readings
2| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.287 read on another version | On for this account, and not off by default | on | on | on |
| v2.1.281 read on another version | Off in both readings | off | off | 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.
Flag server, over time
16| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| this account | on | 2026-11-02T13:05:04Z | 2026-11-12T12:45:04Z | v2.1.316 to v2.1.322 |
| anonymous | on | 2026-10-17T05:30:04Z | 2026-11-12T12:45:04Z | v2.1.302 to v2.1.322 |
| this account | off | 2026-11-02T12:55:05Z | 2026-11-02T12:55:05Z | v2.1.316 |
| this account | on | 2026-11-01T20:45:05Z | 2026-11-02T12:40:07Z | v2.1.316 |
| this account | off | 2026-11-01T20:40:05Z | 2026-11-01T20:40:05Z | v2.1.316 |
| this account | on | 2026-11-01T20:25:04Z | 2026-11-01T20:30:06Z | v2.1.316 |
| this account | off | 2026-11-01T20:20:05Z | 2026-11-01T20:20:05Z | v2.1.316 |
| this account | on | 2026-10-07T18:00:12Z | 2026-11-01T19:30:06Z | v2.1.292 to v2.1.316 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-09-29T08:25:05Z | 2026-10-17T05:10:04Z | v2.1.284 to v2.1.302 |
| this account | off | 2026-10-07T17:59:34Z | 2026-10-07T17:59:34Z | v2.1.293 |
| this account | on | 2026-09-29T10:00:07Z | 2026-10-07T17:10:05Z | v2.1.284 to v2.1.292 |
| this account | off | 2026-09-28T18:05:09Z | 2026-09-29T08:25:05Z | v2.1.283 to v2.1.284 |
| anonymous | off | 2026-09-23T10:55:04Z | 2026-09-29T07:25:04Z | v2.1.280 to v2.1.284 |
| this account | on | 2026-09-28T18:02:35Z | 2026-09-28T18:02:35Z | v2.1.284 |
| this account | off | 2026-09-23T11:00:06Z | 2026-09-28T16:35:05Z | v2.1.280 to v2.1.283 |
One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.
First cited
1The earliest release whose published evidence quoted tengu_mcp_legacy_url_elicitation was v2.1.287, 1 Oct 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
1Build by build
38One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
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.