How to fix Claude stuck loading history/projects?

ClaudeErrors & BugsUpdated March 7, 2026
Quick Answer

Start with a clean session (sign out, clear cache/cookies, disable extensions), then verify permissions/plan, check service incidents, and retry on another network. If it persists, capture error details and follow the steps below.

Step-by-Step Fix

  1. Confirm the scope

    • Test another browser/device and another network.
    • Note whether the issue is account-specific or device-specific.
  2. Refresh authentication and local state

    • Sign out, clear site data (cookies + cache), then sign in again.
    • Disable extensions temporarily (ad blockers, privacy tools).
  3. Check plan/permissions

    • Verify you’re using the correct account/workspace.
    • Confirm your plan is active (if relevant) and permissions are sufficient.
  4. Apply targeted fixes

    • If this is a network/DNS problem: switch networks, change DNS, disable VPN/proxy.
    • If this is a browser/app problem: try incognito, update the app/browser, reset site settings.
    • If this is a service incident: wait and retry later.
  5. Escalate with evidence

    • Capture error text + timestamps + steps to reproduce.
    • Include OS, browser/app version, and network context (VPN/proxy/firewall).

Common Root Causes

  • Expired sessions or invalid tokens
  • Plan/permission mismatches
  • Extensions or strict privacy settings blocking requests
  • Network filtering (VPN/proxy/firewall/DNS)
  • Temporary outages

Prevention Tips

  • Keep a clean browser profile for critical workflows
  • Avoid stacking multiple request-blocking extensions
  • Document billing owner + workspace permissions
  • Keep screenshots/logs for recurring failures

Claude · Errors & Bugs

More Claude errors & bugs guides

Browse all guides in this category to troubleshoot related issues faster.

Browse all guides →

Frequently Asked Questions

Try an incognito/private window and a second network (hotspot). If it works there, the issue is local (cache/extensions/network filtering).

Related Guides

Continue with nearby guides in the same topic to rule out adjacent causes faster.

Claude Attachments Not Uploading or Failing to Process? Here's the Fix

Claude Pro supports file uploads up to 10 MB per file; supported formats include PDF, Word (.docx), plain text, images (PNG/JPG/GIF/WebP), and most code files. If your attachment fails or won't process, the most common causes are an oversized file, an unsupported format, a stale browser session, or a network/extension block. Clear site data for claude.ai, disable ad blockers, and retry in incognito — that resolves the issue in the majority of cases.

Claude Blank Page / White Screen: Fix Cache, Extensions, and Script Blocking

A Claude blank page or white screen is almost always caused by a stale browser cache, a script-blocking extension, or a VPN blocking WebSocket connections. Open an incognito window and sign in — if Claude loads there, clear all site data for claude.ai in your main browser and disable extensions one at a time. If Claude is blank in incognito too, disable your VPN and check status.anthropic.com for active outages.

Claude error loading chat – How to Fix

Claude's 'error loading chat' message appears when a conversation fails to sync from the server or a browser extension blocks the loading request. Refresh the page once, then try opening the conversation in an incognito window. If a specific chat refuses to load on all devices, that conversation's data may be corrupted on Anthropic's servers — start a new conversation to continue your work.

How to report a Claude bug effectively (what to include)?

Report Claude bugs at support.anthropic.com. An effective bug report includes: the exact error message, the specific steps that reproduce it (not just 'it stopped working'), your browser and OS version, whether it happens in incognito, and whether it affects all conversations or just one. Including a screenshot and the approximate timestamp speeds up resolution significantly.

How to fix Claude error while generating (stops mid-response)?

Claude stopping mid-response is usually caused by a network interruption, a browser extension blocking the streaming connection, or the response hitting a length or usage limit. The fastest fix is to refresh the page, disable extensions, and retry with a more focused request. If Claude consistently stops at the same point in a response, the content itself may be triggering a safety check — try rephrasing the request.

Claude Something Went Wrong: Causes and Fixes

The 'something went wrong' error in Claude is a generic message that covers session issues, browser problems, and temporary server errors. Start by refreshing the page and signing out then back in. If the error persists, clear your browser cookies for claude.ai and try a private window. This error almost never indicates an account problem — it is usually a temporary connection or session issue.