How to Delete a Claude Project Without Losing Needed Work

Deleting a Claude project is permanent: the project instructions, uploaded knowledge files, and the conversations linked to it are removed together. There is no archive option that keeps the project visible but inactive. Before you delete, spend a few minutes on two questions: what in this project needs to go somewhere else, and can you get the same result by clearing conversations or updating the instructions instead?

The decisions, rules, and progress notes that made the project useful are the things most worth saving. fenbs keeps those in a separate record that travels with the work rather than the tool, so they remain available whether you rebuild in Claude or move to a different assistant.

Deletion versus clearing versus archiving

Claude Projects does not have a built-in archive mode at this time. Your choices are to keep the project as-is, delete individual conversations within it, update the instructions to repurpose it, or delete the project entirely. Clearing individual conversations removes chat history but leaves the project instructions and knowledge files intact. Updating the instructions changes how Claude behaves in future conversations without touching past ones.

If the project is just cluttered but still useful, clearing old conversations is often enough. If the instructions are out of date but the project structure is still right, rewriting the instructions is less disruptive than deleting. Deletion makes sense when the project itself is the problem: the name is wrong, the files are all wrong, or the project belongs to someone leaving the team.

What to save before you delete

Project instructions are the most valuable thing to preserve. Copy them to a document or a dedicated tool before deleting. If the instructions evolved over time and earlier versions were better in certain ways, note those differences.

• The project instructions in full, with any notes about why each rule exists.
• Decisions made during the project: what was agreed, by whom, and the reasoning.
• The list of uploaded knowledge files and where each one came from, so you can find the source if a future project needs the same material.
• Any unfinished tasks and their current status, including what was done and what the next step is.
• Outputs worth keeping: summaries, drafts, or analysis that might be referenced later.

Keeping this information in a tool like fenbs means it outlasts the Claude project and is available to a connected assistant in any future session. For guidance on what context is worth preserving long-term, Claude project memory covers the choices in more detail.

How to delete a Claude project

Before deleting, do a final check of the list you assembled. Re-read the project instructions once and confirm that any rule you want to keep in a future project is copied out. For a project with uploaded files, note which files you will need to re-add and where they came from. Taking three minutes here saves significantly more time during a rebuild.

Open the Claude project you want to delete. Look for a settings or options menu—usually accessible from the project name or an icon near the top of the sidebar when the project is selected. The exact navigation depends on the current Claude interface, so check the Anthropic help center↗ (opens in a new tab) if you cannot find the delete option. You will typically be asked to confirm the deletion before it completes.

On the mobile app, the delete option is usually in the project settings accessible from the same menu. If you are a member of a shared project rather than the owner, you may not have permission to delete it. Contact the project owner or your organization administrator in that case.

After deletion: picking up the work

If you saved the project instructions before deleting, creating a new project and pasting them in takes a few minutes. Adding the same files to the new project restores the knowledge base. If you kept the decisions and task status in fenbs, a connected assistant can read that context in the new project immediately.

If the work is moving to a different AI tool rather than a new Claude project, the saved context travels with it. The instructions become reference material; the decisions and progress notes tell the next assistant what was agreed and where things stand. See how to organize Claude Projects for more on structuring project context so it remains useful across changes.

How to do this with fenbs

1. Create a free account and set up your project in fenbs before deleting the Claude project.
2. Paste the Claude project instructions into fenbs as Decisions and rules. Keep the reasons, not just the instructions.
3. Add each unfinished task to the fenbs board with its current status and next step noted.
4. Delete the Claude project once the context is saved in fenbs.
5. When you set up the next project—in Claude or elsewhere—ask the connected assistant to read the fenbs project context first so it starts with the full picture.

If the project has shared members, make sure the relevant people have access to the saved context before you delete. The goal is that nobody loses work they were counting on.