Why Is the Claude Not Working?
If Claude is not working right now, open status.claude.com before you touch a single setting and see whether claude.ai or Claude Code is flagged. If everything shows as operational, the problem is almost always on your side: a stale browser session, an extension, a VPN, an outdated app, or a terminal that has no idea what Shift+Enter means. Most of those fixes take under five minutes.

Quick Troubleshooting Guide:
| Problem / Symptom | Best Fix | Difficulty / Time |
| Claude won’t load, or chats hang or error out | Check status.claude.com, then hard refresh or try a private window | Easy / 2 min |
| Claude not working today for everyone | Confirm the incident on the status page, then wait and retry | Easy / 0 min |
| Claude login not working or stuck in a loop | Use your original sign-in method, clear claude.ai site data, turn off VPN | Easy / 5 min |
| Sign-in email never arrives | Check spam, confirm the address, request one fresh email | Easy / 3 min |
| Claude app not working on iPhone or Android | Force close, switch networks, update, then reinstall as a last step | Easy / 5–10 min |
| Claude desktop app not working | Quit fully, update, restart, check firewall, then reinstall | Moderate / 10–15 min |
| Claude Code Shift+Enter submits instead of adding a new line | Run /terminal-setup, or type \ then press Enter | Moderate / 5 min |
| Only fails on work or school Wi-Fi | Test on a phone hotspot, then ask IT about filtering | Moderate / varies |
Work top to bottom. The early fixes are the most likely and the least risky, and the advanced ones come later for a reason.
Claude Not Working Today? Rule Out an Outage First
Anthropic runs a public status page at status.claude.com that lists claude.ai, the Claude Console, the API, and Claude Code as separate components. That split matters. Claude Code can be throwing errors while claude.ai works fine, and the reverse can happen too.
- Open status.claude.com in a new tab. It is hosted separately from the main app, so it usually loads even when Claude doesn’t.
- Find the component you actually use (claude.ai, Claude Code, or the API). A yellow or red marker means Anthropic already knows.
- Read the newest incident update. It normally says what’s affected: sign-in, a specific model, voice mode, or chats in general.
- If the page is green but you still can’t get in, check Downdetector for a spike in reports. Occasionally a problem starts before an official incident is posted.
Real-world example: Past incidents logged on the status page have included authentication errors hitting claude.ai and Claude Code at the same time. So if one login fails, try the other surface before you change anything on your device.
Tip: If it’s a confirmed outage, do not clear data, uninstall anything, or reset your password. Wait 10 to 15 minutes and retry. Most posted incidents are resolved within minutes to a few hours.
Claude AI Not Working in Your Browser: Fixes in Order
When Claude AI is not working on claude.ai and the status page is clean, work through these in sequence.
Fix 1: Hard refresh and start a new chat
Plenty of “Claude is not working” moments are really one stuck conversation. Reload the page with Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac), then open a fresh chat and send a short test message. If the new chat works, your old one is the problem. Copy anything important out of it and carry on in the new one.
Fix 2: Try a private or incognito window
Open claude.ai in a private window. If it works there, something stored in your normal browser (cookies, cache, or an extension) is interfering. That narrows things down fast.
Fix 3: Turn off browser extensions if claude not working
Ad blockers, privacy tools, script blockers, and VPN extensions are the usual suspects. Disable them, reload, and re-enable them one at a time until the problem returns. The last one you turned on is your culprit.
Fix 4: Clear site data for claude.ai only
- Open your browser settings and find the list of site data or cookies.
- Search for claude.ai.
- Remove only those entries, not your entire browsing history.
- Close the tab, reopen claude.ai, and sign in again.
Warning: Clearing site data signs you out. Make sure you know which sign-in method you use (Google or email) and that you can still open that inbox before you do this.
Fix 5: Turn off your VPN or switch networks
Switch to a phone hotspot for a minute. If Claude works there, your home router, DNS, VPN, or a work or school firewall is the issue, not your account. Disconnect the VPN and test again before blaming anything else.
Fix 6: Check your date, time, and browser version
A wrong system clock can break secure connections, and an outdated browser can choke on modern web apps. Turn on automatic date and time, then update your browser and restart it.
Fix 7: Make sure you haven’t simply hit a usage limit
Sometimes Claude isn’t broken at all. If you’ve reached your plan’s usage limit, Claude shows a message saying so. There’s nothing to fix in that case. You wait for the limit to reset or look at your plan options.
Claude Login Not Working: What to Try
Claude login not working usually shows up as one of four things: a sign-in loop that dumps you back on the login page, a generic error after you sign in, a verification email that never arrives, or a login that works but shows an empty account.

Use the same sign-in method you originally used
If you created your account with Google, use the Google button. If you used an email link or code, use that. Signing in with a different method than the one you started with is a frequent source of confusion, and it can look like your chats vanished. Try each method you might have used before assuming anything is lost. This is a likely explanation rather than a guaranteed one.
If the sign-in email never arrives
- Check spam, junk, and promotions folders.
- Confirm the address has no typo.
- Request one new email, then wait a few minutes. A newer email may replace an older one, so use the latest.
- On a work address, company mail filters can delay or block messages. Try again later or ask IT.
If you are stuck in a login loop
- Open a private window and try signing in there.
- If that works, clear claude.ai site data in your normal browser (see Fix 4 above).
- Disable extensions and turn off your VPN.
- Try a different browser entirely.
If login fails only on your phone
Update the app, force close it, and sign in again. If that fails, test the same account in a mobile browser. If the browser works, the app is the issue, and you can move to the reinstall step below.
Tip: A login failure that hits everyone at once is often an incident, not your account. Check the status page before you start changing passwords or sign-in methods.
Claude App Not Working on iPhone or Android
When the Claude app is not working on your phone, the cause is usually the network, an old app version, or a stuck session.

- Force close the app and reopen it.
- Switch networks: Wi-Fi to cellular, or the other way around. If it works on one and not the other, the first network is the culprit.
- Update the app from the App Store or Google Play.
- Restart your phone.
- Sign out and sign back in.
- As a last step, uninstall and reinstall the app.
Warning: Before reinstalling, make sure you know which sign-in method you use, and copy out any unsent drafts. Anything you’ve typed but not sent won’t survive.
Real-world example: Past status-page incidents have called out specific features, such as voice mode, alongside sign-in and chat errors. If only one feature fails and the rest of the app works, that points to a service issue rather than your phone.
Claude Desktop App Not Working: Step-by-Step Fixes
If the Claude desktop app is not working but claude.ai works in your browser, the problem lives in the app or on your computer, not in your account. Use the browser version as your workaround while you fix it.
- Quit the app completely. Closing the window isn’t enough. On Windows, check the system tray. On Mac, press Cmd+Q or quit from the menu bar. Then reopen it.
- Check the status page. Desktop-app problems have appeared in Claude’s incident history before, so rule that out first.
- Update the app to the latest version, then restart your computer.
- Check your VPN, firewall, and antivirus. Security software can block an app’s connection even when your browser connects fine. Temporarily pause the VPN to test.
- Sign out and back in inside the app.
- Reinstall the app, downloading it only from Claude’s official download page.
Warning: Reinstalling can reset local app settings. If you configured connected tools or integrations by hand, note them down first so you can set them up again. Never download the installer from a third-party site.
Claude Code Shift+Enter Not Working: Why It Happens and How to Fix It
You’re writing a long prompt in Claude Code, you press Shift+Enter for a new line, and the whole half-finished thing gets sent. Frustrating, but it’s rarely a bug in Claude Code itself. In many terminals, Shift+Enter sends exactly the same signal as plain Enter, so Claude Code can’t tell the difference. The fix is to teach your terminal to send something different, or to use another key combo.
Fix 1: Type a backslash, then press Enter
Type \ at the end of the line and press Enter. That inserts a new line without sending the prompt. It’s the quickest workaround and it works regardless of terminal.
Fix 2: Run /terminal-setup if claude not working
- Open Claude Code in a supported terminal or editor, running directly (not inside tmux or screen).
- Type /terminal-setup and press Enter.
- Follow the prompt, then fully restart your terminal or editor.
- Type a few words and press Shift+Enter to test.
Warning: This command changes your terminal or editor keybindings. If you’ve customized those settings heavily, back up the file first. Also, re-run it if you switch to a different editor.
Fix 3: Try Option+Enter on a Mac if claude not working
Option+Enter inserts a new line in many setups. If it types a strange character instead, your terminal has to be told to treat Option as the Meta (Esc+) key, which is a setting in the terminal’s preferences.
Fix 4: Leave tmux or screen first
Terminal multiplexers can swallow the key signal that /terminal-setup relies on. Exit the multiplexer temporarily, run /terminal-setup in the terminal directly, then reattach.
Possibilities worth knowing about
- VS Code extension quirk: there is a GitHub issue reporting that Shift+Enter inserts a stray backslash along with the new line in the VS Code extension, while Option+Enter works cleanly. I’m not aware of a confirmed fix, so use Option+Enter as the workaround.
- Windows with WSL2: one reported case had Shift+Enter submitting the prompt in Windows Terminal with WSL2. The backslash method worked as a stopgap.
- After an update: terminal behavior can change between Claude Code versions. If Shift+Enter worked before and stopped, re-run /terminal-setup after updating.
Why Is Claude Not Working? Common Causes and Symptoms
Only the first cause below is documented on Anthropic’s own status page. The rest are well-known reasons web apps fail, so treat them as likely suspects, not a diagnosis.
- Service-side errors or an outage. Symptom: errors for many people at once, chats failing, or sign-in problems. Confirm on the status page.
- A stale session or old cookies. Symptom: login loops, or pages that half-load.
- Extensions, VPN, or firewall interference. Symptom: works on your phone hotspot or in a private window, but not in your normal browser.
- An outdated app or browser. Symptom: features missing, crashes, or an app that won’t open after a long gap between updates.
- A usage limit. Symptom: Claude tells you the limit was reached rather than throwing a vague error.
- Sign-in method mismatch. Symptom: you can log in, but your account looks empty.
- Terminal key handling (Claude Code only). Symptom: Shift+Enter sends the prompt.
Advanced Fixes When Nothing Else Works
Test on a second device and a second network
Try the same account on another device, then on a different network. If it fails everywhere, suspect the account or an outage. If it only fails in one place, the problem is local to that device or network.
Flush your DNS cache
- Windows: open Command Prompt and run ipconfig /flushdns.
- Mac: open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. It will ask for your admin password.
Try a different DNS server
Switching your device to a public DNS service can help if your provider’s DNS is flaky. Write down your current settings first so you can switch back.
Warning: Changing DNS or router settings affects every app on that device or network. Do it only after the simpler fixes have failed, and note your original values.
Create a fresh browser profile
A brand-new profile has no extensions, cookies, or cached data. If Claude works there, your old profile is the problem, and you can rebuild it slowly.
Update or reinstall Claude Code if not working
If Claude Code itself misbehaves, update it with claude update, run claude doctor to check your installation, and use /logout followed by /login to refresh your sign-in. If the problem persists, reinstall using Anthropic’s current installation instructions.
Warning: Back up any custom configuration before reinstalling, and make sure you know which account you’re signing in with.
Check your work or school network
If Claude only fails on a managed network, a content filter may have changed. Ask your IT team to confirm that claude.ai isn’t being blocked or inspected. Don’t try to bypass the network rules yourself.
How to Prevent Claude From Breaking on You
- Bookmark status.claude.com so your first check takes five seconds.
- Know your sign-in method. Write down whether you use Google or email so a login problem never turns into a guessing game.
- Keep a backup route. If the desktop app fails, use the browser. If the browser fails, try the phone app.
- Copy long prompts before sending them. A failed request or a closed tab can lose everything you typed.
- Keep apps and browsers updated, and restart them occasionally.
- Run `/terminal-setup` once per terminal if you use Claude Code daily, and re-run it after switching editors.
- Keep conversations focused. Start a new chat when a thread gets unwieldy instead of fighting one that keeps erroring.
When to Seek Professional Help
Most Claude problems clear up on their own or with the steps above. Reach out for help when:
- The status page is green and the problem follows your account across devices and networks. Contact Claude support through the help center, and include the time it happened, your browser or app version, the exact error text, and a screenshot.
- Billing or account access is the issue. Support handles these. Troubleshooting from your side won’t.
- It only fails on a work or school network. That’s an IT conversation.
- It fails on one computer only, even after a clean browser profile and a reinstall. Security software, a damaged system file, or malware could be involved, and a technician should take a look.
- You get sign-in emails you didn’t request. Secure your email account first, then contact support.
Conclusion
When Claude is not working, resist the urge to reinstall. Check the status page first, then work from the lightest fix (a refresh or private window) to the heavier ones (clearing site data, reinstalling, changing DNS). For Claude Code, the Shift+Enter problem is almost always your terminal, and a backslash plus Enter or a quick /terminal-setup handles it. Fix the cheap things first, and you’ll usually be back in a chat within minutes.
Frequently Asked Questions:
Occasionally a problem starts before an official incident is posted. More often, it’s local: a stale session, an extension, a VPN, or a network filter. Test in a private window and on a phone hotspot to see which side the problem is on.
You may be using a different sign-in method than the one you created the account with, such as email instead of Google. A stale session or blocked verification email can also cause it, as can an authentication incident on Anthropic’s side. Try your other sign-in methods, a private window, and the status page.
Not necessarily. If claude.ai loads in your browser but the desktop app doesn’t, the issue is probably the app or your computer. Quit it fully, update it, check your VPN or firewall, and reinstall only as a last step.
Your conversation history is tied to your account, not only your device, so reinstalling shouldn’t delete it. You will need to sign in with the correct account again, and unsent drafts and any hand-configured local settings won’t carry over.
Type a backslash at the end of the line and press Enter, or try Option+Enter on a Mac. For a lasting fix, run /terminal-setup directly in a supported terminal, then restart it.
