Claude Projects Broken? What to Check Before Starting Over

"Broken" can mean different things for a Claude project: you cannot open it, the knowledge files are not being read, the instructions are not applying, or responses have become unreliable. Each cause has a different fix, and mixing them up leads to deleting something you did not need to delete. The first step is identifying which category the problem belongs to.

Whatever the cause, keeping decisions and unfinished work somewhere outside Claude means a session does not have to start from nothing while the project is being fixed. fenbs stores that context separately so any connected assistant can continue from the same point.

Project access problems

If you cannot open a project at all—it does not load, shows an error, or has vanished from the sidebar—the likely causes are a plan change, a different organization context, or a temporary sync issue. A plan downgrade removes access to Projects entirely. An organization switch means you may be viewing a different workspace from the one that holds the project. A hard refresh or a sign-out and sign-in resolves most sync issues.

Check the Anthropic status page↗ (opens in a new tab) for any current incident before spending time on other fixes. A service disruption can make projects unreachable temporarily without indicating deletion or any change on your side. For a full walkthrough of access problems, Claude Projects disappeared has step-by-step checks.

File and knowledge base problems

If you can open the project but Claude is not drawing on the uploaded files, a few things are worth checking. Files that failed to process sometimes show a status indicator beside the file name; removing and re-uploading the file usually resolves this. Very large files, unsupported formats, or files that are mostly images rather than text may not index well. Check the Anthropic help center↗ (opens in a new tab) for the current list of supported file types and any size constraints.

Asking Claude directly whether it can see the contents of a specific file is a quick diagnostic. If it answers that it cannot find the information, the file may not have processed correctly. Re-uploading a clean copy typically fixes the problem. For detailed steps on adding and updating files, uploading files to Claude Projects covers the process.

Keeping source file links in a separate record is a useful habit even when the project is working. If a file needs replacing, the original source is already tracked. fenbs keeps Links and listings alongside the project work, so the team does not have to reconstruct where each file came from.

Project instruction problems

Project instructions tell Claude how to behave in every conversation within the project. If instructions are not applying—Claude ignores a tone rule, forgets a constraint, or seems to reset to default behavior—check whether the instructions are complete and unambiguous. Contradictory instructions, very long instruction text, or instructions that conflict with Claude's own guidelines can all cause inconsistent behavior.

Start a new conversation within the project and ask Claude to summarize the instructions it has been given. Compare that summary to your actual instruction text. If the summary is incomplete or wrong, rewrite the instructions more clearly and test again. Keep a copy of the working instructions outside the project so they are not lost if you need to delete and recreate it.

Service-side and intermittent problems

Claude can give unreliable or degraded responses during periods of high load or partial outages even when the project itself is intact. If responses are unusually short, repetitive, or clearly wrong, and nothing in the project has changed, check the Anthropic status page before editing the project setup. Retrying the same prompt in a fresh conversation in the same project is a quick test for whether the issue is session-specific or project-wide.

A problem that appears in one conversation but not another is usually session context rather than a broken project. Start a new conversation, give it the same task, and compare the result.

Preserve the work before taking drastic action

Deleting a project removes the instructions, the uploaded files, and the conversation history linked to it. If the project is genuinely broken beyond the fixes above, extracting what you need before deletion saves rebuilding work later. Copy the instructions, note which decisions were made and their reasoning, and record where each piece of unfinished work stands.

Keeping that record in fenbs means the next session—whether in a rebuilt Claude project or a different tool—starts from a known state. See Claude project memory for more on what context is worth saving and how to structure it for the next session.

How to do this with fenbs

1. Create a free account and add your project to fenbs so the work record exists independently of the Claude project.
2. Paste your Claude project instructions into fenbs as Decisions and rules. Include the reason for each rule, not just the rule itself.
3. If the Claude project needs to be deleted and rebuilt, the fenbs record provides the exact instructions and decisions to repaste into the new project.
4. At the end of each session, ask the connected assistant to save Where we left off in fenbs with the current task status and next step.
5. If Claude is unavailable or degraded, continue the work with any connected assistant using the same fenbs context.