What a Claude Project really is: a container that holds related chats, files, and instructions — so every conversation inside shares the same context and memory.

Projects — Containers for Your Chats, with Shared Context

The difference between a pile of loose chats and an organized workspace with a memory.

Working draft — 2026-06-06

Why This Asset Exists

Most people run their whole Claude life as one long, undifferentiated list of chats. A hundred conversations, no structure, and the same background information re-pasted into every single one. Projects fix both problems at once: they organize your chats and give them a shared memory.

But people misunderstand what a Project is. They think “a folder of chats.” It’s more than that — and the part they miss is the part that matters: shared context.

The One-Sentence Version

A Project is a container for related chats — and everything you put in it (files + instructions) becomes shared context that every chat inside can see.

A Project Is a Container

Tie a Project to one goal — “Q3 Marketing,” “Home Renovation,” “Client X.” Every chat you start inside that Project stays inside it, instead of scattering into your global history.

That alone is the cure for chat sprawl. When you have 100, 200 conversations, a Project is how you keep all the ones about a single goal in one place — and how you actually find them again tomorrow.

The Key Idea: Shared Context

Here’s the part most people miss. A Project isn’t just a folder — it’s a shared context that every chat inside it inherits.

You give the Project two things, once:

Knowledge — files and reference text.
Instructions — how Claude should behave.

And then every chat you start in that Project automatically sees both. You don’t re-upload the brand guide. You don’t re-explain the tone. You set it once at the Project level, and all the conversations inside share it.

The mental model: a Project is a room. Everything you hang on the walls — the files, the instructions — is visible to every conversation that happens in that room.

The Two Things You Give a Project

1. Knowledge (the Project’s memory)

Upload the things Claude should always have on hand: PDFs, Word docs, spreadsheets, images, or pasted text like your brand voice, a style guide, or a meeting transcript. This becomes the Project’s memory — shared by every chat inside. Load it once; never paste it again.

2. Instructions (how Claude behaves here)

Custom instructions tell Claude how to act in this Project. The cleanest way to write them is the CRAFT recipe — Context, Role, Action, Format, Tone (see Structured Prompting). Set the role, the format, and the tone once, and every chat in the Project starts there.

Why This Also Saves You Tokens

A Project keeps your context scoped. Claude pulls in this Project’s files — not everything you’ve ever uploaded — so conversations stay lean, fast, and sharp. (More on why that matters in Models, Tokens & Usage.) Organizing isn’t just neat; it’s cheaper and it gets better answers.

Chat Projects vs. Cowork Projects

One thing to keep straight so it doesn’t trip you up later: a Chat Project (what this asset is about — organizing conversations in claude.ai) is not the same as a Cowork Project (a folder on your computer that Claude works inside). Same word, different things. We’re talking about Chat Projects here. Cowork Projects come later, when you graduate to execution.

When to Make a Project

Make one whenever you have a goal with more than one conversation and context you’d otherwise re-paste. A trip, a launch, a client, an ongoing initiative. If you catch yourself re-explaining the same background in chat after chat — that’s the signal to make it a Project.

Common Confusions

“Isn’t a Project just a folder of chats?” No — that’s the part people miss. A folder just groups. A Project also shares context — its files and instructions reach into every chat inside it.

“Do all the chats in a Project really see the files?” Yes. That’s the whole point. Anything in the Project’s knowledge is available to every conversation in it.

“If I update the instructions, do old chats change?” New messages follow the current instructions. Think of the Project’s instructions and files as the standing context every new turn is built on.

⚠️ “Is Projects free?” Historically Projects has been a paid (Pro) feature — check your plan. (Verify current gating before teaching it as free.)

Landmark Language

A Project is a container for your chats — tied to one goal.
The magic isn’t the folder, it’s the shared context.
Set it once; every chat inside inherits it.
A Project is a room — the files and instructions on the walls are visible to every conversation in it.
Knowledge = the Project’s memory. Instructions = how it behaves.
A Chat Project is not a Cowork Project — same word, different thing.

Say these often. The goal is for someone to stop treating chats as disposable and start building a Project the moment a goal has more than one conversation.