Why Does Claude Take So Long? Checks and Practical Fixes

Claude takes a long time for one of four main reasons: a service problem on Anthropic's side, a conversation or uploaded file that has grown very large, a complex task that genuinely needs more processing time, or a tool call that has stalled. Each cause has a different fix, and identifying which one you have is faster than trying them all.

Before restarting a session or closing a tab, take a moment to check which problem you are dealing with. A quick check often saves work that would otherwise be lost. When you do need to open a fresh session, tools like fenbs keep a task checkpoint outside the conversation so the next session can continue from the right place.

Is Anthropic's service slow right now?

Check the Anthropic status page at status.anthropic.com before trying anything else. Look for an active incident on the Claude row. A degraded or partial outage status means the delay is on Anthropic's side, not yours. Refreshing the page, switching browsers, or starting a new chat will not speed things up while an incident is active. You can use the is Claude down guide for a broader look at reading service status and deciding whether to wait or switch tools.

A clear status page does not guarantee perfect service, but it shifts the probability toward a problem in your own session. If the status is clear and you are still seeing unusual delays, move on to checking the session itself.

Does a long conversation make Claude slower?

Yes. Claude receives the full conversation history with every new message, because the model has no persistent memory between individual turns. A long session carries more text to process than a fresh one, and response times climb as the conversation grows. You may notice this as responses that were quick at the start of a chat becoming noticeably slower after an hour of work.

Large file uploads also contribute to this effect. Uploading a lengthy PDF or a large code file adds to the amount of context Claude must process with each new turn. If a session slowed after you uploaded a file, the file size is likely part of the cause. The fix in both cases is to start a new session and supply only the context needed for the next task.

Is Claude working on a complex task?

Some tasks take longer because the model is doing more work. Writing a detailed technical document, reasoning through a multi-step problem, or running a task that involves tool use such as web search or code execution can take a minute or more. That is not a fault; it is the model applying more effort to a problem that requires it. The expected response time scales roughly with how complex the request is.

If you are using an extended thinking mode, Claude works through its reasoning process before delivering a response, which adds noticeable time. If you triggered that mode intentionally for a complex problem, the wait is expected. If it appears on simple questions, check your model or prompt settings.

Is a tool call stalled?

When Claude uses external tools, such as web search, code execution, or a connected service like fenbs, the session waits for each tool to return a result. A slow or temporarily unavailable external service can stall the session at the tool-call step without producing an error message. In Claude Code, this appears as the terminal waiting on a shell command, file operation, or test run.

If Claude appears stuck partway through a task with no new output arriving, check whether a tool or subprocess is still running. In an agentic session, a pending approval or a failed background command can stop progress silently. Interrupting the current run and checking the state of any running processes is a faster diagnosis than waiting indefinitely.

What to try when Claude is taking too long

• Check status.anthropic.com for an active incident before changing anything else.
• Start a new chat if the current session has more than 20-30 exchanges or contains large files.
• Break a large request into smaller sequential steps to reduce per-response processing time.
• For large files, try working with a shorter excerpt focused on the specific question you have.
• In Claude Code, check whether a tool call, test, or background command is still pending.
• Try the Claude mobile app or a different browser if the web page is unresponsive.

What about delays in Claude Cowork?

Claude Cowork uses the same underlying model. The same checks apply: service status, session length and task complexity. A Cowork session that involves multiple collaborators or shared files may carry more context than a standard solo session, which can contribute to slower responses during busy periods. Check the Anthropic status page first, then consider whether the session has grown unusually large.

How to do this with fenbs

1. Create a free account at fenbs.ai.
2. Add the current project: its goal, tasks and any decisions or rules that apply.
3. Connect Claude over MCP from Integrations using the setup guide for Claude.
4. At the start of a new session, ask Claude to read the fenbs context, including Rules and Where we left off.
5. Before ending a long or complex session, ask Claude to save progress to the relevant tasks and update the project's Where we left off with the next step and anything waiting on you.

For related slowness in ChatGPT, see why does ChatGPT take so long. For a general overview of what Claude is and what it can do, what is Claude AI is the starting point.