Fix: Claude Not Responding to Prompts Today

If you click the "Send" arrow or press Enter and Claude does not generate any output—or the typing indicator blinks indefinitely without printing text—you are likely experiencing a silent client-server disconnection. Unlike explicit error messages, this behavior points to interrupted data streaming. Follow these steps to restore active communication with Claude's servers.

1. Diagnose and Force-Reset Stuck WebSockets

Claude transmits its responses to your browser using a continuous stream via Server-Sent Events (SSE) or WebSockets. If this stream is interrupted by an IP change or a micro-outage, the interface will hang silently.

1. Press F12 (or Cmd + Option + I on Mac) to open the developer console.
2. Click on the Console tab and look for errors such as WebSocket connection failed or Failed to load resource: net::ERR_CONNECTION_CLOSED.
3. Perform a hard refresh to discard the stale socket connection: press Ctrl + F5 on Windows, or Cmd + Shift + R on macOS.
4. Try sending a basic, one-word prompt like "test" to see if the server establishes a new stream.

2. Clear Claude-Specific Service Workers and Site Data

Browsers store local application states and service workers to speed up load times, but corrupt local files can block outbound API requests.

1. While on the Claude.ai website, click the lock icon to the left of the URL in your browser's address bar.
2. Click on Site settings.
3. Select Clear data to purge all cached databases, cookies, and local storage.
4. Alternatively, navigate to your browser's settings page, search for "Cookies and site data," select "See all device data and permissions," search for "claude.ai," and delete the entries.
5. Log back into your account and test the prompt input.

3. Identify and Disable Restrictive Browser Extensions

Aggressive ad-blockers, script-blockers, or privacy extensions can mistakenly flag Claude's event-stream packets as tracking scripts, silently dropping them.

1. Open an Incognito/Private window in your browser (this disables most extensions by default).
2. Log into your account at claude.ai and test a prompt.
3. If Claude responds, an extension is blocking the traffic. Return to your standard window and temporarily disable extensions like uBlock Origin, Privacy Badger, or any third-party VPN/antivirus browser add-ons.
4. Whitelist *.claude.ai and *.anthropic.com in your security extension settings.

4. Force a Routing Path Change via Mobile Hotspot

Sometimes domestic ISPs or localized CDN servers experience routing loops that drop TCP connections to Anthropic's hosting infrastructure.

1. Turn off your computer's Wi-Fi connection.
2. Enable the personal hotspot on your cellular mobile device.
3. Connect your computer to your mobile hotspot.
4. Reload Claude.ai and submit your prompt. If this works, the bottleneck is your local router's DNS configurations, firewall settings, or your ISP's routing path to Anthropic. Resetting your home router or switching to a public DNS provider (like Cloudflare's 1.1.1.1 or Google's 8.8.8.8) will permanently fix this.

When to escalate

If Claude remains completely unresponsive across multiple browsers, different network connections, and multiple devices (e.g., both computer and mobile app), your account's rate limit block or internal profile status may have become corrupted. Open a ticket with Anthropic Support (support.anthropic.com) and provide the console log exports showing the failing API endpoints.