[BUG] Claude Code hangs indefinitely on large MCP tool responses without user feedback

Resolved 💬 4 comments Opened Mar 20, 2026 by eksanwl510-wq Closed Mar 23, 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?

When get_design_context is called on a large Figma node via MCP, Claude Code enters "Considering..." state and hangs for hours with no timeout, no error message, and no indication that the request is too large to process. Expected behavior: return an error or warning when the response exceeds processable size, instead of silently hanging.

What Should Happen?

When a Figma node is too large to process, Claude Code should immediately return a clear error message such as: "The selected node is too large to process. Please select a smaller section or individual frame." It should never silently hang in a "Considering..." state without any timeout or user feedback.

Error Messages/Logs

Steps to Reproduce

  1. Connect Figma MCP to Claude Code
  2. Open a Figma file with a large page or frame
  3. Share the Figma URL with a large node-id (e.g. full page node)
  4. Ask Claude Code to work on the page using get_design_context
  5. Claude Code enters "Considering..." state and hangs indefinitely with no error, no timeout, and no user feedback

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.80 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

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