Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.280entry #336

Claude Code v2.1.280 ·

New request tracking for MCP elicitation dialogs

Claude Code now separately tracks MCP elicitation requests across telemetry, dialogs, and request verification

Group of 4 Under the hood Internal Changes
JSON All of v2.1.280
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release

What

  • A new elicitationOutboundRequestIds set tracks outbound requests tied to MCP "elicitation" (a protocol feature that lets a server ask the user for input), alongside the existing knownOutboundRequestIds, automatedOutboundRequestIds, and deviceOutboundRequestIds sets, and is cleared along with them on reset.
  • A new dialog kind constant, dialog:mcp_elicitation, was introduced for these dialogs.
  • The request-ID attestation check, which validates that inbound and outbound requests correlate correctly, now also checks this new set.
  • Pending-action republish telemetry (tengu_pending_action_republished) now reports elicitation as its own survivor_kind category, separate from dialog and permission.

Why This lets Claude Code track, verify, and report on MCP elicitation requests as their own category instead of lumping them in with other dialog or permission requests, keeping telemetry and request verification accurate for this MCP feature.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding only shows the tracking set being added, not what elicitation requests are used for or how they surface to the user.

See this entry in the whole of v2.1.280 →

Feedback