Elicitations let plugins ask users for input mid-task, such as confirming a refund or filling in a missing detail.

We’re adding support for MCP Tasks and Elicitations in Claude. Tasks let Claude give plugins long-running jobs such as deep research and report back when they’re done.

Tasks and Elicitations are available today in the Claude Code CLI, rolling out to more Claude products soon. Building plugins for Claude? Add Tasks and Elicitations to your MCP server today.

Mid-task questions are where parallel agents stall for us. With several CLIs open side by side, the hard part is noticing which one is waiting. Does an elicitation also fire the Notification hook, so a terminal can flag it?

Ya, Please do a weekly reset. I can't use it because there's no limit; it's max 20

In the financial world a refund confirm only counts if the user saw the exact amount and payee. With elicitation the plugin writes that prompt itself. Does Claude show which server is asking, or can any plugin pop a form that looks like Claude?

What happens if the user answers 20 minutes later? Does the plugin re-check the refund amount, or act on what it saw before asking?

It's ridiculous that a large company like yours doesn't offer a text search feature in the chat. Secondly, we can't upload compressed files to the project section because you don't allow it. It's extremely frustrating.

The confirm step is where people decide if they trust the agent. What worked for me: show exactly what it will do, "Refund $129.00 to Dana's card for order 48213", not "Allow payments.refund?". People approve vague prompts without reading them.

Nice, the useful part is the server pausing mid-task and resuming with the user's answer instead of failing the tool call. For refunds I'd keep the confirmation schema strict (enum/boolean, not free text). Are you planning to gate destructive tools behind elicitation by default?

claude plugins can now stop mid-task and ask you to confirm a refund. that's the default i'd want in every ai paste at the top of any chat today: "before anything that spends, refunds or deletes, stop and ask me. never guess a missing detail"

I don't need an AI that never interrupts me, just one that asks before the refund.

elicitations is a nice one, sometimes claude starts my minecraft render without asking how long it should be and i have to start over

.... But I've been using elicitations already how is this any different?

asking mid task beats guessing on a refund every time