Claude Code / AI Coding Tools

Claude Code Session Stopped Responding on Long MCP Tool Calls

Fix Claude Code UI watchdog killing sessions on long-running synchronous MCP tool calls Includes evidence for Claude Code troubleshooting demand.

Source-backed Last updated May 12, 2026 1 source Needs local verification

Category: AI Coding Tools
Error signature: The session stopped responding. Send your message again to resume with a fresh process.
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 12, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Claude Code, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

The session stopped responding. Send your message again to resume with a fresh process. is a Claude Code failure pattern reported for developers trying to fix claude code ui watchdog killing sessions on long-running synchronous mcp tool calls. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Long-running synchronous MCP tool calls (>10-12 min) trigger UI watchdog with message 'The session stopped responding. Send your message again to resume with a fresh process.' Not an API timeout (API_TIMEOUT_MS=900000), but a UI-level health check. Reported May 12, 2026.

Common causes

When a synchronous MCP tool call blocks Claude Code's worker for ~10-15 minutes, the UI watchdog declares the session dead and shows 'The session stopped responding' — even though the MCP call may still be processing. This orphans MCP server processes and breaks long-running workflows.
Long-running synchronous MCP tool calls (>10-12 min) trigger UI watchdog with message 'The session stopped responding. Send your message again to resume with a fresh process.' Not an API timeout (API_TIMEOUT_MS=900000), but a UI-level health check. Reported May 12, 2026.

Quick fixes

Confirm the exact error signature matches The session stopped responding. Send your message again to resume with a fresh process..
Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match The session stopped responding. Send your message again to resume with a fresh process. exactly before applying the quick fix.
Compare the failing environment with Claude Code versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does The session stopped responding. Send your message again to resume with a fresh process. mean in Claude Code?

The session stopped responding. Send your message again to resume with a fresh process. indicates the workflow described by "Claude Code Session Stopped Responding on Long MCP Tool Calls" failed in a AI Coding Tools context. Start by confirming the exact signature and the component that emitted it.

What should I check first for The session stopped responding. Send your message again to resume with a fresh process.?

Check whether this cause matches your environment: When a synchronous MCP tool call blocks Claude Code's worker for ~10-15 minutes, the UI watchdog declares the session dead and shows 'The session stopped responding' — even though the MCP call may still be processing. This orphans MCP server processes and breaks long-running workflows.

Is the The session stopped responding. Send your message again to resume with a fresh process. guidance source-backed?

The "Claude Code Session Stopped Responding on Long MCP Tool Calls" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for The session stopped responding. Send your message again to resume with a fresh process.?

For "Claude Code Session Stopped Responding on Long MCP Tool Calls", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging The session stopped responding. Send your message again to resume with a fresh process.?

For "Claude Code Session Stopped Responding on Long MCP Tool Calls", collect the failing Claude Code command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.