[BUG] MCP tool permission approval doesn’t unblock the tool call

Status Open
Reported on v2.1.233
Maintainer reply None cached
Activity 0 comments · opened Aug 17, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Title: MCP tool permission approval doesn’t unblock the tool call

Description:
A tool call from a connected MCP server (add_repo, and separately get_session, both on the same server) returns MCP tool call requires approval and triggers a permission prompt in the client UI. Tapping “Allow once” on the prompt does not resolve it — the next attempt of the same tool call returns the identical MCP tool call requires approval error again. This happened consistently across multiple attempts, including after fully closing and reopening the app. The prompt visually renders correctly (screenshot available) and tapping it produces no visible error, but the underlying tool call state never clears.

Impact: Blocks attaching any new GitHub repository to the session, since add_repo never completes.

What Should Happen?

Tapping allow once should allow it

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

  1. In an active session, call an MCP tool that requires approval (in this case, add_repo from the claude-code-remote MCP server)
  2. Approve it via the in-client permission prompt
  3. Retry the same tool call — it still returns MCP tool call requires approval instead of executing

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.233

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗