Claude.ai: Projects, Conversations, and the Interface

The Interface at a Glance

Claude.ai is organized around two concepts: conversations and Projects. Understanding the difference between them is the first step to using Claude efficiently.

A conversation is a single chat thread. Everything Claude knows about your context is limited to what appears in that conversation window. When you start a new conversation, Claude has no memory of previous ones. This is not a bug — it is a deliberate design choice. Each conversation starts fresh, which prevents context from one task contaminating another.

A Project is a persistent workspace. It has its own custom instructions and a knowledge base of documents you upload. Every conversation you start inside a Project inherits that context automatically — without you having to re-explain your situation every time.

Setting Up Your First Project

Projects are the most underused feature in Claude.ai. Most users treat every conversation as independent — they re-explain their role, their preferences, and their context every single time. Projects eliminate that repetition.

To create a Project:

1. In the left sidebar, click New Project
2. Give it a descriptive name (e.g., "Work — Marketing Copy" or "Personal — Research")
3. Add custom instructions in the Project Instructions field — describe who you are, what you're working on, and how you want Claude to respond
4. Upload any relevant documents — style guides, reference materials, product specs, your own previous writing
5. Start a conversation inside the Project

Claude will now apply your instructions and reference your documents automatically in every conversation in that Project — without you having to repeat yourself.

What to Put in Project Instructions

Project instructions are the most powerful input you can give Claude. They set the tone, context, and expectations for every conversation in the Project. Good instructions answer:

• Who are you and what do you do? ("I am a freelance marketing consultant specializing in B2B SaaS companies.")
• What is Claude's role in this Project? ("You are my writing assistant. Help me draft clear, persuasive copy in an approachable but professional tone.")
• What are your preferences? ("Always write in active voice. Keep sentences under 25 words. Use UK English spelling.")
• What should Claude avoid? ("Never use jargon or corporate buzzwords. Do not pad content with filler sentences.")

The Knowledge Base

Every Project has a knowledge base where you can upload documents. Claude reads these documents and references them when answering questions in the Project. This is useful for:

• A style guide or tone of voice document you want Claude to follow
• A product specification sheet or company background document
• Your own previous writing so Claude can match your voice
• Research documents or reports you want to analyze across multiple conversations

Documents in the Project knowledge base are cached and do not count against your per-message context limit — a significant advantage for longer reference documents.

Organizing Multiple Projects

There is no limit to the number of Projects you can create. A practical structure for most professionals:

• One Project per major work area (writing, coding, research, client X)
• One personal Project for planning, goals, and personal tasks
• One learning Project for topics you are actively studying

Start a new conversation inside the appropriate Project every time you begin a new task. Your context is already there. You can start working immediately.