Follow Discord
Sweep 30 Oct 2026 · 21:36Z Build v2.1.315 533 read Stable v2.1.308 Latest v2.1.314 Next v2.1.315 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.315 ·

Pending MCP elicitation requests are carried with other pending prompts

Waiting MCP elicitation requests are now kept in session state and sent with pending permission and dialog requests, then removed before delivery

Group of 2 Use it now No documentation found New Features
JSON All of v2.1.315
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
AgentsArea: what it touches
New FeaturesKind: in v2.1.315,
What probably matters to youSection of the release

What

An MCP elicitation is a question an MCP server (an outside tool Claude Code connects to) asks you through Claude Code. Claude Code already kept track of pending permission requests and pending user dialogs so they could be sent again. Elicitation requests now join them:

  • The session's state snapshot now includes pending_elicitation_requests next to pending_permission_requests and pending_user_dialog_requests.
  • The reply sent when a client first connects (the initialize response) can now carry pending_elicitation_requests.
  • The SDK, and the handler for worker responses, strip this field from the reply before passing it on, as they already did for the other two.
  • If these fields turn up on a reply that is not the first-connect reply, they are ignored and a note is logged.

Why

In practice, an MCP server's question that is still waiting for an answer is now tracked like a waiting permission prompt, so it can be offered again to a client that connects later.

Read from
Names in the bundlepending_elicitation_requests

See this entry in the whole of v2.1.315 →

Feedback