Clicking a notification while a multiple-choice question is open cancels the question (acts like Escape)
Status Open
Reported on v2.1.207
Maintainer reply None cached
Activity 3 comments · opened Jul 12, 2026
What happens
When a session needs input, I get a Windows toast notification in the lower-right corner. If that notification is for a question the session is asking me (the multiple-choice / select-an-answer prompt), clicking the notification cancels the question — the prompt dismisses exactly as if I'd pressed Escape, and the session is left with no answer.
Expected
Clicking the notification should just focus/bring the app forward so I can answer the question. It should not dismiss or cancel the pending prompt.
Steps to reproduce
- Have a session reach a point where it asks a multiple-choice question (the popup answer selector).
- A toast notification for that question appears in the lower-right corner.
- Click the notification.
- The question prompt is cancelled (as if Escape was pressed) instead of being brought into focus.
Impact
The natural gesture — click the notification to go answer — is the exact gesture that throws the answer away. I have to ignore the notification and click into the app manually instead.
Environment
- Claude Code 2.1.207
- Windows 11 Home (10.0.26200)
- Notification: Windows toast, lower-right
3 Comments
Still open and still relevant. Clicking the Windows toast for a pending multiple-choice question cancels the question rather than focusing the app, so the session is left with no answer and stalls.
Worth cross-referencing #88850, which has the same shape on a different surface: a chat message sent while
AskUserQuestionis open is reported to the model as a user dismissal. In both cases an interaction that should be neutral, or at worst a no-op, is delivered to the model as an explicit cancel. They may well share a fix.This was marked stale by the sweep with no maintainer response. Commenting to keep it in the queue, and glad to supply a recording or version details if that would move it.
I came here to write up this same bug. Adding my info.
AskUserQuestion prompt is silently dismissed by a permission approval in another session
With two Claude Code sessions open concurrently:
Session A calls AskUserQuestion; its picker renders.
Session B raises a tool-permission prompt.
Clicking Allow in session B causes session A's question picker to disappear without being answered.
Session A's tool call returns "The user did not answer the questions."
Impact: the model is told the user declined to answer when they were never given the chance. If it then proceeds on a default, it builds against a decision the user never made. Failure is silent on both sides — the user sees the prompt vanish, the model sees a non-answer.
Expected: a permission decision in one session should not dismiss an unrelated question prompt in another; question state should be per-session.
Environment: Claude Code on Windows 11, two concurrent sessions in separate working directories.
Still open. @mikejcook's case is a third trigger for what looks like the same defect: approving a permission prompt in one session dismisses an open question in another. In this report the trigger is clicking the Windows toast for the question. In #88850 it is sending a chat message while the question is open.
All three end the same way. The model is told the user did not answer, when the user was never given the chance to. If the model then proceeds on a default, it builds on a decision nobody made.
Three unrelated gestures producing one wrong result suggests the fix may sit in one place: what the question prompt treats as a dismissal.