You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.312,
ImprovementsSection of the release
What
MCP tools come from MCP servers, separate programs that give Claude extra tools. When a permission prompt is answered from a remote or SDK host with an allow decision, that answer can now carry an approvalTicket.
The ticket is stored for that tool call and server.
It is attached as anthropic/approvalTicket on the later MCP call, only in the main conversation and only for the same server.
The ticket is removed from the stored answer.
The remote control layer keeps approvalTickets and a takeApprovalTicket hook, and clears them when the prompt is settled.
The same finding also changes the session event writer. It gains keepsApiErrorRequestId, tickets, stateRowTypesWritten and streamedResponseId, and loses startRowWaits, timersBehindStartRows and personsMessageReceived.
Why
An MCP server can now receive proof that a host approved the call, in remote and SDK setups.
