Why Is Claude Not Working? Common Reasons and Fixes

Nothing derails deep work faster than watching your AI assistant freeze mid-task or throw a vague network error right before a deadline. Whether you are staring at a spinning loader on claude.ai, seeing a “Couldn’t connect to Claude” banner on your desktop app, or watching Claude Code fail inside your terminal, finding Claude not working is frustrating especially when your internet connection appears completely fine.

The good news is that almost every Claude interruption falls into one of two buckets: a temporary server-side issue at Anthropic, or a local configuration conflict on your machine that takes less than five minutes to resolve.

In this troubleshooting guide, you will learn how to quickly check if Claude is down today, fix browser and login errors, resolve Claude Desktop connection bugs, and get Claude Code running smoothly again in both your terminal and VS Code.

Quick Diagnostic Checklist: Is Claude Down Today or Is It Your Setup?

Before you reinstall apps or change system settings, spend 60 seconds identifying where the breakdown is actually happening.

  1. Check the Official Claude Status Page: Open the official Anthropic Claude Status page. Anthropic tracks individual components separately including claude.ai, the Claude API (api.anthropic.com), Claude Code, and workspace connectors. If a component shows Degraded Performance or Partial Outage, the issue is on Anthropic’s end and local troubleshooting will not fix it.
  2. Test Across Surfaces (Browser vs. Desktop vs. Mobile): If the desktop app refuses to connect, try opening claude.ai in an incognito browser window. If the browser works while the desktop app fails, your network is healthy and the issue is isolated to the desktop client.
  3. Switch to a Mobile Hotspot Briefly: If neither the browser nor the app loads, switch your computer to a phone hotspot for one minute. If Claude loads immediately on cellular data, your home router, ISP DNS, or corporate firewall is blocking the connection.

Pro Tip: Status pages occasionally lag behind real-time traffic spikes by 10 to 15 minutes. If status.claude.com shows all green lights but you are still seeing authentication or capacity errors, check live community threads on r/ClaudeAI or r/ClaudeCode before wiping your local configuration.

Common Reasons Why Claude AI Is Not Working (Web & General Access)

If you are asking “why is Claude AI not working today?” while using the web interface, one of these four culprits is almost always responsible.

1. Server Outages and “Overloaded” Capacity Errors

During peak US business hours or immediately following major model releases, Anthropic’s inference servers can experience heavy demand. You may see messages like “Due to unexpected capacity constraints, Claude is unable to respond” or an API 529 Overloaded error.

  • How to fix it: Wait two to five minutes before retrying rather than spamming the refresh button. If one specific model is experiencing elevated errors as sometimes happens during partial model-specific incidents switch to another available Claude model in the model selector dropdown.

2. VPNs, Corporate Proxies, and Browser Extensions

Anthropic uses strict security and regional routing checks. Active VPNs, privacy proxies, and aggressive ad blockers frequently trigger silent authentication failures or infinite loading loops.

  • How to fix it: Disconnect your VPN completely and reload the page. Next, test Claude in a private/incognito window with all browser extensions disabled. If it works there, whitelist claude.ai in your ad blocker or privacy extension.

3. Session Usage Limits and Oversized Chat Threads

Claude enforces rolling 5-hour session limits and weekly usage caps depending on your subscription tier. Additionally, extremely long conversations filled with large PDFs or codebases can hit context ceiling errors.

  • How to fix it: Check for a banner indicating when your 5-hour session limit resets. If your chat stops responding mid-generation without a limit warning, start a fresh conversation and paste a brief summary of your progress rather than continuing a massive thread.

4. Corrupted Cookies or an Incorrect System Clock

Stale authentication tokens in your browser cache can cause login redirects to fail. Less obviously, if your computer’s date and time are out of sync by even a few minutes, TLS security handshakes with Anthropic’s servers will fail automatically.

  • How to fix it: Clear site data and cookies specifically for claude.ai and anthropic.com, then sign back in. Ensure your operating system is set to Set time automatically.

How to Fix “Couldn’t Connect to Claude” on Claude Desktop

Seeing the “Couldn’t connect to Claude. Please check your network connection and try again” error on the Claude Desktop app even while your browser works fine. It is one of the most reported issues among desktop users. Because Claude Desktop runs inside an Electron wrapper, local cache corruption or proxy handling can break its connection independently of your web browser.

Follow these steps in order to restore the desktop app:

  1. Force-Quit All Background Processes: Closing the window often leaves background helper processes running. Open Task Manager (Windows) or Activity Monitor (macOS), end all Claude processes, and relaunch the app.
  2. Check for App Updates: Outdated desktop builds frequently fail authentication after backend updates. Open the app menu, click Check for Updates, or download the latest installer directly from claude.ai/download.
  3. Reset Local App Configuration Data: After certain OS or package updates, local configuration files inside the Claude Desktop directory can become corrupted. Fully quit the app, rename your local config folder as a backup, and relaunch:
    • Windows: Press Win + R, type %APPDATA%, and rename the Claude folder to Claude.bak.
    • macOS: Open Finder, press Cmd + Shift + G, go to ~/Library/Application Support/, and rename Claude to Claude.bak.
    • Linux: Run mv ~/.config/Claude ~/.config/Claude.bak in your terminal.
  4. Use the Web App as an Immediate Fallback: If you are on a corporate network using a strict PAC proxy file, Electron-based desktop apps can occasionally receive HTTP 403 blocks while standard browsers pass through cleanly. Keep claude.ai open in your browser so your work isn’t stalled while IT whitelists the desktop client.

Troubleshooting Claude Code Not Working in Terminal and VS Code

For developers relying on Anthropic’s agentic CLI tool, Claude Code not working usually stems from environment path issues, credential overrides, or IDE extension mismatches.

1. Fixing command not found: claude in Terminal

If you just installed Claude Code and your terminal says zsh: command not found: claude or ‘claude’ is not recognized, your shell does not know where the binary lives.

  • Restart your terminal completely: PATH updates never apply to terminal windows that were already open during installation.
  • Add ~/.local/bin to your PATH (macOS/Linux): Per the official Claude Code troubleshooting documentation, native installations place the binary in ~/.local/bin. Run this command to register it permanently:
Bash

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc

(Replace ~/.zshrc with ~/.bashrc if you use Bash on Linux.)
  • Prefer the native installer over npm: If you have conflicting global npm installs and native binaries, run which -a claude (macOS/Linux) or where.exe claude (Windows). Remove duplicate npm copies and reinstall using Anthropic’s native one-line installer to avoid Node permission errors.

2. Resolving Login Loops and Leftover API Key Conflicts

If Claude Code repeatedly asks you to log in, throws an “organization disabled” error, or bills the wrong account, check for a hidden environment variable.

  • Unset stale API keys: An old ANTHROPIC_API_KEY stored in your shell profile silently overrides your Claude Pro or Max subscription login. Run unset ANTHROPIC_API_KEY in your terminal, remove it from your .zshrc or .env file, and authenticate again.
  • Verify your plan eligibility: Claude Code requires a paid Claude Pro, Max, Team, Enterprise, or funded Console API account. Free-tier accounts cannot authenticate into Claude Code.
  • Unlock macOS Keychain: After macOS updates, a locked login keychain can block credential storage. Running security unlock-keychain ~/Library/Keychains/login.keychain-db resolves persistent macOS login loops.

3. Fixing Claude Code Not Working in VS Code

When Claude Code is not working in VS Code such as the /ide integration failing to detect your editor or the sidebar extension freezing run through these targeted checks:

  1. Launch claude from inside VS Code’s integrated terminal: Open VS Code first, open the built-in terminal (Ctrl + ~), and run claude from your project root so the CLI binds to the active workspace socket.
  2. Update both the CLI and the VS Code extension: Version mismatches between the terminal binary and the VS Code extension frequently break diff views and file-editing hooks. Run claude update in your terminal and update the Claude Code extension inside VS Code’s Extensions panel.
  3. Check Windows PowerShell vs. WSL paths: On Windows, opening a project in Windows Explorer while running Claude Code inside WSL (or vice versa) can break IDE detection. Keep both your VS Code workspace and your terminal session inside the same environment.

4. Run claude doctor for Automated Diagnostics

Anthropic builds a self-diagnostic command directly into Claude Code. Whenever the CLI behaves unpredictably, run:

Bash

claude doctor

This command inspects your installation path, authentication state, shell configuration, MCP server connections, and context usage, then proposes automated fixes. If a custom hook or third-party MCP server is crashing your session, launch claude –safe-mode to temporarily disable all customizations and isolate the culprit.

Quick Reference Troubleshooting Matrix

Use this table to match your exact symptom to the fastest solution:

Symptom / Error MessageMost Likely CauseImmediate Fix
“Due to unexpected capacity constraints…”Peak server load or temporary model congestionWait 2–5 minutes and retry, or switch to another Claude model.
“Couldn’t connect to Claude” (Desktop)VPN interference, outdated app, or corrupted local configTurn off VPN, force-quit app, rename local Claude config folder, and relaunch.
“Temporarily unable to authenticate”Anthropic login service incidentCheck status.claude.com; stay signed in and retry once resolved.
zsh: command not found: claude~/.local/bin missing from terminal PATHAdd ~/.local/bin to ~/.zshrc or ~/.bashrc and open a new terminal.
Claude Code login loop / wrong billingLeftover ANTHROPIC_API_KEY overriding subscriptionRun unset ANTHROPIC_API_KEY and re-authenticate.
Claude Code freezes or uses high CPUBloated context window or massive node_modules scanRun /compact inside the session and add build folders to .gitignore.

What Reddit Users Recommend When Claude Keeps Failing

If you search “Claude not working Reddit”, experienced users across r/ClaudeAI and r/ClaudeCode consistently highlight a few practical habits that prevent workflow interruptions before they happen:

  • Compact early in Claude Code: Instead of waiting for auto-compaction to fail or freeze on huge repositories, run /compact manually after finishing each logical coding milestone.
  • Keep a secondary model workflow ready: Power users avoid single-vendor downtime by keeping a backup workflow ready when Anthropic experiences partial outages. If you are comparing alternatives for coding or automation, check out our guide on Best AI Agents in 2026: Ranked, Tested & Explained and our step-by-step tutorial on How to Get Started with Claude AI for Building an AI Agent.
  • Audit your MCP servers: Many sudden “Claude not working” reports in Desktop and Claude Code are actually caused by a single misconfigured Model Context Protocol (MCP) server timing out on startup. Run /mcp inside Claude Code to see which connector is failing to initialize.

Frequently Asked Questions (FAQs)

Why is Claude AI not working right now even though my Wi-Fi is fine?

When your internet works on other websites but Claude fails to load, the cause is usually either a partial Anthropic server outage, an active VPN or browser extension blocking authentication requests, or an out-of-sync computer clock breaking security certificates. Check status.claude.com first, then test claude.ai in an incognito browser window with your VPN turned off.

Why does Claude Desktop keep saying “Couldn’t connect to Claude”?

This error typically happens when Claude Desktop’s local Electron cache becomes corrupted after an update or when a corporate proxy blocks desktop app traffic. Force-quit all Claude processes, rename your local Claude configuration folder (%APPDATA%\Claude on Windows or ~/.config/Claude on Linux), and restart the app.

Can I use Claude Code on a free Claude account?

No. Claude Code requires an active paid subscription (Claude Pro, Max, Team, or Enterprise) or a funded Anthropic Console API account. If you try logging into Claude Code with a free account, authentication will fail repeatedly.

How do I fix Claude Code not working in VS Code’s integrated terminal?

First, make sure you launch claude directly inside VS Code’s integrated terminal from your project root folder. Next, run claude update to ensure your CLI version matches the latest VS Code extension, and run claude doctor to verify that IDE integration permissions are enabled.

Why does Claude suddenly stop responding in the middle of a long chat?

Long conversations consume your available context window and hit token or session limits faster. If a long thread stalls or throws an interrupted response error, ask Claude to summarize the key points so far, then paste that summary into a brand-new chat window.

Summary & Next Steps

Most Claude not working errors come down to three quick checks: verifying live server status on status.claude.com, disabling VPNs or stale API keys, and resetting corrupted desktop or CLI configurations. By keeping claude doctor in your developer toolkit and knowing when to switch from the desktop app to your browser during proxy blocks, you can recover from interruptions in minutes instead of losing an afternoon.

Looking to get more reliability and automation out of your AI stack? Explore more practical tutorials and tool comparisons on Future AI Blog, including How to Use AI Agents for Email Sorting and Hire vs. Build: Best AI Sales Agents in 2026 and subscribe to our newsletter for weekly AI troubleshooting guides and workflow breakdowns.

Leave a Comment