Claude Projects Disappeared? Checks and Recovery Steps

When Claude Projects stop appearing, the cause is almost never permanent loss. The most common reasons are a plan that no longer includes Projects, the wrong organization context in the sidebar, a collapsed section, or a short sync delay after a service hiccup. Running through each check takes a few minutes and usually finds the issue before anything is genuinely gone.

If the work inside a project matters beyond the current session, keeping decisions and progress somewhere outside Claude is good insurance regardless. fenbs stores that record separately from any AI app, so a session in a different tool can continue from the same point while you restore access.

Check your account plan first

Claude Projects is available on paid plans. If a subscription lapsed, a billing charge failed, or the account was downgraded, the Projects section can disappear from the sidebar without any prominent warning. Sign in to your Claude account settings and confirm that your current plan includes Projects. The Anthropic help center↗ (opens in a new tab) lists which plans support the feature and what each plan includes.

A trial period ending is another frequent cause. Checking the billing tab for a plan-change notice or a failed payment takes under a minute and is worth doing before contacting support.

Check which organization you're viewing

If you belong to more than one Claude organization, you may simply be viewing the wrong one. A project created inside a work workspace does not appear on a personal account, and vice versa. Look for a workspace or organization switcher near the top of the sidebar and confirm you are in the correct context.

Team and Enterprise accounts separate personal and organizational projects. If a colleague created the project inside a shared org, you need to be viewing that org to see it. Switching context takes one step in the switcher and does not require signing out.

Look for a display or browser issue

The Projects section in the Claude sidebar can be collapsed without leaving a clear indicator. Expanding it, or scrolling down past other sidebar items, is worth trying before concluding nothing is there. A hard refresh—Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac—forces the browser to discard its cache and reload the page fresh. Opening an incognito window rules out a browser extension or a stale session cookie making the sidebar render incorrectly.

If Projects are not appearing on a phone, the steps differ slightly. The guide to Claude Projects on mobile covers the phone-specific checks, including what syncs between devices and how to force a refresh in the app.

Check for a sync delay or service problem

Projects sync across signed-in devices, but a service disruption can leave the sidebar temporarily showing stale data. The Anthropic status page↗ (opens in a new tab) shows ongoing incidents and recent resolutions. After a disruption, waiting a few minutes and reloading the page almost always restores the correct view.

If one device shows your projects and a second does not, a forced sign-out and sign-in on the second device almost always resolves it. Confirm both devices are signed into the same account and viewing the same organization before trying anything more involved.

Understand what deletion actually means

A project can be deleted by any member with the right permissions. Deletion removes the project instructions, the uploaded knowledge files, and the conversations linked to it. If you have ruled out the other causes and confirmed the project is genuinely gone, check the Anthropic help center for the current data recovery policy, then contact Anthropic support promptly. Any recovery window, if one exists, is typically short.

Knowing the difference between a hidden project and a deleted one matters before acting. For steps on removing a project deliberately, see how to delete a Claude project. For an overview of the Projects feature, the Anthropic help center explains how instructions and knowledge files work together.

Keep a work record outside Claude

The most valuable part of any project is usually the decisions made, the instructions written, and the current state of the work. If you rebuild that from memory after a problem, the process is slow and imprecise. Storing it in a separate tool means that recovering Claude Projects access is not the only path back to productive work. For more on structuring project context so it survives tool changes, how to organize Claude Projects is a practical guide.

How to do this with fenbs

1. Create a free account and add your active project to fenbs before any problem occurs, not after.
2. Copy your Claude project instructions into fenbs as Decisions and rules. Include the reason for each rule so a future session understands the intent, not just the instruction.
3. At the end of each Claude session, ask the connected assistant to save Where we left off in fenbs: what was completed, what changed, and the next step.
4. If Claude Projects becomes unavailable, open fenbs and read the project context. Any connected assistant can continue from that record using the same board.
5. When access is restored, use the fenbs record to bring the Claude project instructions back in line with any decisions made in the meantime.

You can also link to related existing posts from Claude Projects in a shared workspace to see how teams handle the same challenge of keeping context when access is interrupted.