Claude Cowork, With and Without CRAFT
CRAFT for Claude Cowork · Honest Comparison
CRAFT isn’t a rival to Claude Cowork — it runs inside it. This page shows what Cowork does on its own and what the CRAFT layer adds — starting with proof, not claims.
Proof before pitch: this is what continuity looks like
CRAFT’s whole argument is that your working state should be a file you can read — so here’s one. Every CRAFT session ends by writing a handoff like this, and the next session starts by reading it:
Handoff excerpt — structure real, project details invented
done_today: pricing page draft v2; reviewer notes applied
decisions: keep three tiers; annual-billing copy deferred to H015
open_items:
– #3 competitor screenshots — waiting on teammate
– #5 FAQ draft — half done, resume at “refunds” section
next_session_first_move: reread reviewer notes, finish FAQ #5
watch_out: /final/ folder is client-approved — do not edit
Two weeks later, a brand-new session reads that file and picks up mid-stride — decisions intact, half-done work resumed at the right line. Nothing on this page claims more than that file shows: everything below works the same way, as plain text in a folder you own.
What you’ll notice in week one
Not everything below lands on day one. These three do — they’re where most people feel the difference first.
Nothing starts cold
Your first handoff file gets read by your second session — and the re-explaining tax you’ve been paying just stops. see the tutorial →
It teaches itself
Say “turn on tutorial mode” and CRAFT walks you through your first real session from inside your own project. see the tutorial →
Same task, same quality
The second time you run a recipe, you notice what’s missing: the drift. Results stop depending on how well you prompted today. see the tutorial →
Where Cowork alone has no counterpart
These seven aren’t upgrades to something native — without CRAFT, this lane is simply you, doing it by hand. That’s why they get the visual weight on this page.
Lessons that compound
The mistake you already made in March, made again in July — because nothing wrote it down.
A lessons-learned file records mistakes and discoveries once; every session re-reads it at boot. The work sharpens over months instead of resetting.
Cowork alone: insights persist only if memory happens to retain them.
Quality and drift control
Tuesday’s output was sharp. Thursday’s was mush. Same tool, same you.
Validator recipes, review gates, and consistency checks give the work a written quality bar every session can reach for. how it catches mistakes →
Cowork alone: quality rides on how well each conversation is prompted.
Upgrade safety
You want the new version — but not badly enough to risk three months of work.
Framework and your work live in separate folders. Upgrading is a folder swap with a built-in check that proves your work was untouched — and a rollback path if you want the old version back. how upgrades work →
Cowork alone: not applicable — there’s no framework layer to upgrade.
Verifiable releases
You downloaded something that will sit inside your working sessions. Is it what the author published?
Every CRAFT release is versioned and ships with SHA256 checksums and a signature — you can verify the download is exactly what was published.
Cowork alone: no signed-checksum step for the things you install.
Credential hygiene
An API key pasted into a chat window is a key you’ve lost track of.
A written discipline: credentials live in a dedicated ignored folder — never in chat, never in files that leave your machine.
Cowork alone: no standing convention for secrets across sessions of work.
Working with other AI tools
You use more than one AI — but handing work between them means retyping context and hoping you didn’t paste something private.
A structured way to hand research out to other tools and fold results back in — with a wall that keeps your project’s private material out of outbound prompts. research basics →
Cowork alone: paste findings in by hand and manage what crosses over yourself.
Project management spine
Week three of a two-month project: what’s decided, what’s stalled, what did we learn in week one?
A standing to-do list, subprojects with charters and phase gates, and lessons capture — connective tissue for work that spans weeks or months. see the tutorial →
Cowork alone: longer arcs live in your own notes.
Where both have a layer — and what CRAFT adds
Cowork does real work in each of these rows on its own. The right column is the structure CRAFT adds on top — read these as “and,” not “versus.”
| Capability | Claude Cowork on its own | With CRAFT |
|---|---|---|
| Session-to-session continuity“Where was I on Tuesday?” | Projects carry per-project memory — facts, preferences, background — viewable and editable. What carries over between working sessions isn’t a file you can open and check. | The handoff file at the top of this page — written at close, read at boot, plus checkpoints and a device-switch procedure. see the tutorial → |
| Named specialist personas“I need a different kind of eye on this.” | Skills and styles shape how Claude responds; no built-in roster of named specialists with routing between them. | A named team of specialist personas with an orchestrator that routes work — and reviews that draw on multiple perspectives with recorded confidence scores. see the tutorial → |
| Curated recipe libraries“I don’t want to assemble this from twelve sources.” | Plugins and skills install from marketplaces — assembled piece by piece, from many authors. | Cookbooks: curated, versioned collections designed to work together and pass the framework’s own quality gates. what you get → |
| Build your own“My workflow isn’t in anyone’s library.” | You can author your own skills — a real capability, and a good one. | Author recipes and cookbooks too, in a protected namespace upgrades won’t overwrite, with validation to keep them well-formed. |
| Learning the tool“I don’t have a weekend for docs.” | Good help documentation from Anthropic. | Guided tutorial mode inside your own project, plus a beginner series on this site. start here → |
| Self-repair“Something’s off and I don’t know what.” | Troubleshooting is conversational — describe the problem, work it out. | Built-in diagnostic checks for the framework itself: a doctor to run before there’s a mystery to solve. |
| Delegating to sub-agents“Parallel work that comes back mergeable.” | Cowork can spin up sub-agents for parallel work — powerful, and available to everyone. | Delegation on written contracts: what the agent delivers, in what form, to which file. |
Shared groundBuilt for knowledge work — both of them. Cowork itself is built for real knowledge work, not just coding. So is CRAFT — it assumes no coding background at all; the kitchen does the organizing: recipes, cookbooks, ingredients.
What CRAFT asks of you
Honesty cuts both ways, so here’s the price. Getting started is small: download one zip, unzip it, open the folder in Claude Cowork, and say “Initialize a CRAFT session.” No login, no install, no configuration ceremony. The real cost is a learning curve — CRAFT is a working method, and like any method it takes some sessions before its habits are your habits. Tutorial mode walks that curve with you, and the beginner series covers every step. And because CRAFT structures your work, it adds a little ceremony to it: sessions end by writing things down. That’s the cost. The table above is what it buys.
The honest bottom line
If your Claude use is occasional and self-contained, Cowork alone — with its native memory — is genuinely enough, and we’d rather tell you that than sell you structure you don’t need. CRAFT earns its keep when the same kinds of work recur across many sessions: that’s when written continuity, compounding lessons, and a standing quality bar stop being overhead and start being the reason the work holds. The deeper story on how the two layers fit: What Claude Remembers Now — and What CRAFT Adds.
Try it against this page. CRAFT for Claude Cowork is in free public beta through December 31, 2026 — no login, no paywall, no email gate. Download it, open it in Cowork, and check any claim yourself: every capability above is plain text you can read, starting with a handoff file just like the one at the top. Get the latest release →
This page reflects the framework as it is today and gets updated as CRAFT evolves — counts and capabilities on this site are kept approximate on purpose, because the framework changes faster than marketing copy does.