Getting Started with Projects in Claude

The default experience with Claude is useful, but forgetful. Each chat is isolated. Every time you need Claude to understand your specific context, terminology, or standards, you're copying and pasting the same information.

Projects solve this. They turn Claude into a collaborator with context and one that remembers what matters to your work.

What Projects Are

A Project is a custom workspace inside Claude with three distinct components: a knowledge base, custom instructions, and chat histories that all live together.

The knowledge base holds documents you upload once. Brand guidelines, style guides, reference materials, case studies, technical specifications — anything Claude should reference automatically in every conversation within that project. You upload it. Claude reads it. Every subsequent chat inside that project operates with that knowledge already loaded.

The instructions define how Claude should respond within this project. Tone, perspective, expertise level, format preferences — write these once, and they apply to every chat. If you're building a project for grant writing, your instructions might specify formality, nonprofit language conventions, and a focus on measurable outcomes. If you're building a project for social media content, your instructions might request casual tone, brevity, and emoji usage. Different projects, different instructions.

The chat histories stay organized within each project. Every conversation you have inside a project remains there, searchable and accessible. This is different from your main Claude chat history, which mixes everything together. Inside a project, you see only the conversations relevant to that project's scope.

Projects are especially powerful for teams on a Claude for Work plan. You can share a project with colleagues, control who can view or edit it, and build collaborative workspaces where everyone benefits from the same context. A brand team can create a project with voice guidelines that helps anyone at the organization write consistently. A product team can centralize specs and use Claude to brainstorm features without re-explaining the product every time.

How Projects Improve Context

Claude has a context window — the amount of information it can consider at once. Without projects, you manage that window manually. Copy brand guidelines into the chat. Paste the style guide. Explain the background again. By the time you get to your actual question, you've used a chunk of the available space.

Projects shift that burden. Upload the documents once. Write the instructions once. Then every chat inside the project starts with that context already loaded. Claude considers it automatically alongside whatever you ask.

When you upload a large amount of content to a project, Claude switches to retrieval augmented generation (RAG). Instead of holding everything in the context window at once, Claude retrieves the most relevant pieces based on what you're asking. This extends how much knowledge a project can hold. You can upload an entire course curriculum, a library of case studies, or years of meeting notes, and Claude will pull in the relevant sections when needed.

The difference is subtle but significant. In a regular chat, Claude responds based on what you include in that conversation. In a project, Claude responds based on what you include plus everything in the knowledge base and instructions. The knowledge compounds. The more you build into the project, the more informed Claude's responses become.

Creating Your First Project

Start by clicking "New Project" in the Claude interface. You'll be prompted to name your project and describe what you're trying to achieve. Be specific. "Brand Guidelines" is vague. "Case Study Blog Posts for Wildflower Co." tells Claude exactly what this project is for.

After naming the project, you'll see options on the right side of the screen: star the project for quicker access, edit project details, or archive it when it's no longer active.

Set the Visibility

Choose whether this project is private (only you can access it) or public (shareable with your team if you're on a Claude for Work plan). You can change this later, but deciding upfront clarifies who this project serves.

Write the Instructions

Click "Instructions" and define how Claude should respond inside this project. This is not a place to describe the project again. This is a place to guide Claude's behavior.

Be directive. Claude follows instructions well when they're clear. Vague guidance produces vague results. Specific guidance produces consistent, aligned responses.

Upload Knowledge

Click the "Files" menu and add documents to the project knowledge base. You can upload PDFs, Word documents, CSVs, text files, or connect to Google Drive. Anything uploaded here will be referenced automatically in every chat within the project.

Think about what Claude needs to know to be useful in this context. For a product development project, upload product specs, user research findings, and competitor analysis. For a content project, upload brand guidelines, past blog posts, and editorial calendars. For a financial planning project, upload budget templates and past financial reports.

Once uploaded, Claude processes the files and integrates them into the project's knowledge base. You won't see Claude citing specific pages in every response, but the information shapes how it answers. It's contextual grounding, not rote citation.

Start Chatting

Now you can initiate chats inside the project. Every conversation operates with the instructions and knowledge you've defined. You don't need to re-explain. You don't need to re-upload. Just ask your question or give your prompt, and Claude responds as if it already understands the project context — because it does.

Sharing and Collaboration

If you're on a Claude for Work plan, you can share projects with teammates. There are three permission levels:

Can View: Members can view project contents, access the knowledge base, and chat with Claude, but they can't modify instructions, upload new files, or change settings. Read-only access with discussion rights.

Can Edit: Members have full collaboration power. They can modify instructions, update the knowledge base, add or remove files, manage other members, and contribute actively to the project.

Project Creator: The person who created the project controls everything. They decide who sees it, who can edit it, and whether it's private or visible to the entire organization.

When someone shares a project with you, it appears in the "Shared with Me" tab. You'll receive an email notification. Project creators can modify permissions or remove access as needed. Multiple members can upload documents, create chats, and work together within the same project environment.

This makes projects powerful for team alignment. A marketing team can share a project with brand guidelines so everyone writes with the same voice. A development team can share a project with technical specs so everyone references the same architecture. A nonprofit can share a project with program data so everyone pulls from the same impact metrics.

What Belongs in a Project vs. a Chat

Not everything needs to go into the project knowledge base. Sometimes you need to reference a document without making it permanent project context. Claude handles this too.

When you're inside a project chat, you can upload a file directly in the conversation. That file stays in that specific chat. It doesn't become part of the project knowledge base. Claude reads it and responds, but it won't carry over to the next chat you start in the project.

Use this for one-time context. A colleague sends you a draft document and asks for feedback. Upload it in the chat, ask Claude to review it, and move on. No need to clutter the project knowledge base with temporary materials.

The knowledge base should contain reference materials that apply broadly across all project conversations. The in-chat uploads are for situational needs.

What to Build First

Start with a project that reflects work you're already doing repeatedly. Do you write newsletters every week? Create a project with past newsletters, brand voice guidelines, and instructions about tone and format. Do you manage a product roadmap? Create a project with specs, user feedback, and strategic priorities. Do you plan events? Create a project with past event timelines, budget templates, and vendor contacts.

Pick something narrow enough to define clearly but broad enough to use regularly. A project titled "All Marketing Work" is too vague. A project titled "Monthly Donor Newsletter" is focused and actionable.

Try It Today

Create one project right now. Pick a recurring task you do at least twice a month. Open Claude, click "New Project," and name it after that task. Write three sentences of instructions about how Claude should respond. Upload one document that contains relevant context. Start a chat and ask Claude something you'd normally ask in a regular chat. Notice the difference.

Don't build five projects today. Build one, use it three times, and see if it saves you time. If it does, build the next one.