CRAFT for Claude Cowork · Free Public Beta
Claude’s memory got real. That’s good news — and it’s worth being precise about what it covers, what it doesn’t, and where CRAFT fits.
Credit where it’s due
If you’ve used Claude recently, you’ve noticed: it remembers things now. Projects carry per-project memory — facts about you, your preferences, your background — and you can view and edit what’s remembered. Cowork projects get the same treatment, scoped per project, plus custom instructions. This is genuinely useful, and if you’re using CRAFT, you should use Claude’s memory too. Nothing below is an argument against it.
But “memory” is doing two different jobs in that sentence, and the difference is the whole story.
What native memory holds: what Claude knows about you
Native memory is knowledge about you and your project: who you are, what you prefer, what the project concerns. It accumulates in the background and shapes how Claude responds. It’s the layer that saves you from re-introducing yourself every session — and it does that well.
Here’s what it isn’t designed to hold: how you work. The method you follow for a recurring deliverable. The quality bar a piece of work must clear before it ships. The exact state a project was in when you closed the lid on Tuesday — what was decided, what’s half-done, what’s blocked on whom. The lessons you learned the hard way in March that should change how the work happens in July. That’s not a knowledge-about-you problem; it’s a working-state problem.
What CRAFT holds: how the work gets done
CRAFT keeps that second layer in plain Markdown files that live in a folder you own:
- Session handoffs and boot files — each session ends by writing down exactly where things stand; the next session starts by reading it. What carried over isn’t a black box you hope kicked in — it’s a file you can open.
- Lessons that compound — mistakes and discoveries get recorded once and re-read at every session start, so the work gets sharper over months instead of resetting.
- Recipes and quality gates — your repeatable work becomes named procedures with checks, so results stay consistent instead of drifting with each conversation’s mood.
- Files you can carry and verify — everything is plain text: move it to another machine, put it under version control, check it against a signed release. Your working state is portable because it’s yours.
✓ The one-sentence version: native memory holds what Claude knows about you; CRAFT holds how you work. Different layer — they work together.
Honestly: when Cowork alone is enough
If your Claude use is mostly one-off — a question here, a draft there, a project that lives and dies in a week — native memory plus your own good habits will serve you fine, and CRAFT would be structure you don’t need. CRAFT pays off when the same kinds of work recur across many sessions and the cost of re-establishing context, standards, and state keeps taxing you. That’s the problem it was built for, and it’s the honest boundary of the pitch.
Want the row-by-row view? We keep an honest side-by-side of Claude Cowork on its own versus Cowork with CRAFT — including the rows where native Cowork needs no help: Feature comparison: Claude Cowork with and without CRAFT.
CRAFT for Claude Cowork is in free public beta through December 31, 2026 — no login, no paywall, no email gate. Get the latest release → · Curious about the date? A straight answer about the Beta deadline.
