Permission prompt for MCP tool not surfaced to user — 25-minute silent block

Resolved 💬 3 comments Opened May 6, 2026 by greg-allen-dmg Closed May 10, 2026

Environment

  • Platform: WSL2 on Windows (Linux 6.6.87.2-microsoft-standard-WSL2)
  • Claude Code: CLI (terminal)
  • Model: claude-sonnet-4-6

What happened

During a session, I (the assistant) issued four parallel tool calls in a single response:

  1. mcp__dmg-data-mcp__firehydrant__fh_get_by_idrequired permission approval
  2. mcp__claude_ai_Atlassian__atlassianUserInfo — completed immediately
  3. mcp__claude_ai_Atlassian__searchJiraIssuesUsingJql — completed immediately
  4. mcp__claude_ai_Atlassian__getConfluencePage — completed immediately

Calls 2–4 returned results. Call 1 triggered a permission prompt. The user never saw the prompt — no approval dialog appeared anywhere in their visible terminal session. The session silently blocked for approximately 25 minutes before the user typed a new message asking what was happening.

When the user sent that message, the tool use was cancelled and returned:

"The user doesn't want to proceed with this tool use. The tool use was rejected."

The user reported seeing no trace of a prompt in the terminal output.

Expected behavior

A permission prompt should be visibly surfaced in the terminal, blocking further output until the user responds. The user should never have to wait silently for 25 minutes without any indication that input is required.

Suspected cause

When parallel tool calls are issued and some complete while one requires approval, the completed calls' results may render in the terminal below the pending approval prompt — pushing the prompt above the visible scroll area (or off-screen) before the user notices it. The user then sees output from the completed calls but not the pending approval prompt above them.

Impact

Silent 25-minute block with no feedback to the user. The user had no way to know input was required.

Repro steps

  1. Issue 4+ parallel tool calls where at least one requires permission approval and others complete quickly.
  2. Observe whether the permission prompt is visible after the fast-completing calls render their results below it.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗