Every time you open a new Claude conversation, you start from zero. You re-explain who you are, how you like things structured, what context matters. It works, but it's friction you shouldn't have to deal with every single time.
Claude Projects solves this, and once I set mine up properly, it genuinely changed how I use AI day to day. Here's exactly how I did it and why it works.
The default AI chat experience is stateless. The model doesn't know your name, your role, your preferences, or your working style unless you tell it. Every session. Every time.
For occasional use that's fine. But if you're using Claude for serious work, you're burning time re-establishing context that should already be there.
What you actually want is an agent that already knows the important stuff before you type a single word.
Projects give you a persistent workspace. Inside a Project, you get:
The system prompt is the key part. Whatever you put there becomes the permanent baseline context your agent works from. Every conversation inside that project inherits it automatically.
My setup revolves around two files I upload into every Project I care about.
The User Document is about me. My background, timezone, preferences, the kind of work I do, how I like responses structured. Think of it as a briefing doc the agent reads before every session.
The Soul Document is about how the agent should behave. Its operating principles, its tone, what it should and shouldn't do, how it should handle edge cases. This is where personality and judgment live.
Together, they give the agent both context (who am I talking to) and character (how should I show up).
Once you have those two files, you reference them directly in the Project Instructions:
You are Nash's personal assistant.
Before every session, reference the following files that have been uploaded to this project:
- User.md — Contains personal context about Nash: background, preferences, timezone, and ongoing projects.
- SOUL.md — Defines your core personality, behavior principles, and how you should respond.
Always apply both. User.md tells you who you're helping. SOUL.md tells you how to help.That's it. Now every conversation in this project starts with the agent already oriented. It knows who you are and how to behave before you've typed a word.
Here's where it gets useful at scale.
Say you want a dedicated writing agent, a separate research agent, and another one just for code reviews. Normally you'd have to configure each one from scratch.
With this setup, you just drop both docs into each new Project and update the instructions for that agent's specific focus. The core identity travels with you. You're not starting over, you're extending.
It also means if Claude's Projects feature ever changes, or you want to spin up a new workspace, you're not locked out of your own context. The docs live with you, not inside the tool.
There's a broader ecosystem of tools built specifically around giving AI agents dynamic, cross-session memory. Tools like Mem0, Letta, and Zep extract facts from your conversations over time and retrieve them automatically in future sessions. They go further than what Claude Projects does natively, where each new conversation starts fresh with only your static instructions and uploaded files carried forward.
If you need that level of memory sophistication, those tools are worth exploring. But they come with a tradeoff: you're adding infrastructure, configuration, and another system to maintain.
For my use case, static persistent context through Project Instructions and uploaded docs is enough to get 90% of the value with none of the setup overhead. And crucially, it works natively inside the tools I'm already using.
Honestly, a lot of this comes down to Claude Code.
I spend a significant chunk of my dev time in Claude Code already. Having my Projects, my connectors, and my coding environment all under one roof removes a category of friction I don't want to think about. The context compounds over time. The more you build out your setup, the more useful it gets.
The connectors for Calendar, Gmail, Google Drive, and more are one-click setups inside the Claude interface. No dedicated machine. No gateway to configure. No security hardening before it's safe to run. You connect your accounts and it works.
Switching to a multi-tool stack might give you marginal gains in specific areas, but you pay for it in integration overhead. For people already living in the Anthropic ecosystem, the path of least resistance is to stay there.
On any given day I'm using my Project agent to:
The shift is subtle but real. It stops feeling like a tool you open and starts feeling like a collaborator that's already up to speed.
You don't need my exact files. You need your own version of them. Here's what to cover:
Create a new Claude Project, upload both files, paste your Project Instructions referencing them, and you're live.
Projects and connectors are still evolving. The native integrations will get better, the memory layer will get smarter, and the workflows you can build will get more interesting.
But the core idea, giving your AI persistent identity and context, already works well enough to be worth setting up today. The compounding effect is real. The earlier you build it, the more useful it gets.
If you set something up, share it. I'm @neevash on X.