Back to the Fundamentals: Why I’m Going All-In on CRAFT for Claude Cowork
I didn’t post last week. I’ve been busy thinking — really thinking — about your feedback and rethinking the remaining weeks of the Beta. What I’ve arrived at feels less like a pivot and more like a sharpening. So let me share where things stand and where we’re going.
First: thank you to everyone who has given feedback on CRAFT during the Beta. Every piece of it — the encouragement, the critiques, the feature requests — has been invaluable. I’m not just collecting it; I’m implementing changes right now based on what you’ve told me.
What I’ve Learned (The Short Version)
CRAFT can do many things. Over the past several months, I’ve built it into a framework with over 100 recipes across multiple cookbooks, a multi-persona collaboration system, a structured handoff protocol, a lessons-learned engine, and more. It works across Claude’s web interface, API workflows, and now desktop tools.
But here’s the honest realization: to offer true value, CRAFT must do a few things so well that people who use it will never want to go back to using AI without it. Not everything. A few things. Done exceptionally.
And I now know exactly what those things are — because Claude Cowork showed me.
The Cowork Breakthrough
Anthropic released Claude Cowork recently as a desktop tool for working with Claude on your actual files. It’s powerful. It can read your documents, write code, manage projects, and interact with your computer directly. But it has a fundamental gap: Cowork has no memory between sessions.
Every time you start a new Cowork task, the AI starts from zero. It doesn’t know what you worked on yesterday. It doesn’t remember the decisions you made, the context you built up, or where you left off. For quick one-off tasks, that’s fine. For real, ongoing professional work — the kind that spans days, weeks, or months — it’s a serious limitation.
I’ve now spent four intensive sessions using CRAFT with Cowork on a real campaign project. Here’s what I can tell you from direct experience:
CRAFT turns Cowork from a single-session tool into a multi-session project platform.
That’s not marketing language. It’s what happened. Across those four sessions, CRAFT’s handoff system preserved every decision, every priority, every piece of project intelligence. When Cowork’s context compacted mid-session (the AI summarized the conversation to free up space), my work survived because CRAFT had already written everything to files and committed it to version control. When I switched between sessions across different days, CRAFT restored full context in under a minute — persona state, priorities, file inventory, the works.
Without CRAFT, each of those sessions would have started from scratch. With it, session four picked up exactly where session three left off, with a prioritized task list ready to execute.
Three Things I Now Know For Certain
1. CRAFT exponentially improves the speed, reliability, and ease-of-use of Cowork.
The numbers from my own project tell the story. Four sessions. Twenty-seven accumulated lessons learned. Six git commits preserving every artifact. A handoff system that captures not just what files exist, but why they exist — the thinking, the rationale, the decisions behind them. When context compaction hit, zero work was lost. When a git lock file appeared from a sandbox crash, CRAFT’s recipe system had the recovery steps documented and ready. These aren’t theoretical benefits; they’re things that happened and were handled because the framework anticipated them.
And here’s what surprised me most: Cowork exponentially improves CRAFT. The painful part of using CRAFT has always been the manual copy-and-paste — moving handoff data from the chat into text files, manually saving outputs, switching between the AI conversation and your project files. Cowork eliminates all of that. The AI reads and writes your files directly. Handoffs get written straight to the project folder. Git commits happen inside the session. The framework that used to require careful manual discipline now runs almost automatically.
2. Claude Cowork may be the first of this type of AI interface, but it won’t be the last.
Desktop AI tools that work directly with your files represent a fundamental shift in how people interact with AI. Other companies will follow Anthropic’s lead. The pattern — an AI that operates on your local filesystem with persistent project folders — is too useful to remain a single-vendor feature. CRAFT is positioned to work with this entire category, not just one product.
3. This is the breakthrough I’ve been waiting for, and it happened at the beginning of the Beta.
I’ve been building CRAFT for over a year, designing recipes, testing workflows, refining the handoff system. The missing piece was always the interface — requiring people to manually shuttle information between the AI and their files. Cowork fills that gap. The framework I built for structured AI collaboration finally has a platform that can run it natively. The timing couldn’t be better.
What’s Next
Here’s the plan going forward:
Continue to improve CRAFT specifically for Claude Cowork and promote it to the people who will benefit most. The ideal user is someone who uses Claude Cowork for professional work — projects that span multiple sessions, require accumulated context, and demand reliability. If you have an active GitHub account and a Claude Pro, MAX or Team subscription, CRAFT is built for you. I want to show this audience exactly what’s possible when structured AI collaboration meets a capable desktop tool.
Focus on the fundamentals of CRAFTFramework.ai. The framework works. The recipes work. The handoff system works. But they need to be simpler to use, simpler to understand, and simpler to get started with. That’s where my energy is going.
Simplify recipes and cookbooks. The recipe system is powerful — I’ve built recipes for everything from session initialization to cross-project knowledge transfer to automated compliance auditing. But power without accessibility doesn’t help anyone. I’m working on making the most essential recipes easier to invoke and understand.
Simplify the documentation. If you’ve looked at CRAFT’s documentation and felt overwhelmed, you’re not alone. I hear you. Clearer docs, better onboarding, fewer walls of text.
Simplify the website. Same principle. CRAFTFramework.ai should communicate what CRAFT does and why you’d want it within thirty seconds of landing on the page.
Prepare for a future where CRAFT improves any Cowork-style tool. The architecture is already platform-agnostic at its core — file-based state, structured handoffs, recipe-driven workflows. As more AI desktop tools emerge, CRAFT will be ready.
For Current CRAFT Subscribers
You are not being left behind. Here’s what this means for you:
CRAFT will continue to work the same way it always has. The CRAFT Flavors, the Recipes, the Cookbooks, the Persona system — all of it remains the backbone of the framework. Nothing is being removed or deprecated.
You’ll see a Cowork focus during the remaining Beta weeks. The content, the tutorials, the improvements — they’ll lean toward Cowork integration. But the core framework benefits every Claude workflow, not just Cowork.
All current subscribers will receive lifetime access. I’m creating a new plan specifically for Beta subscribers that gives you lifetime access to CRAFTFramework.ai for as long as I own the CRAFT Framework. You’ll receive a link to this plan soon. This is my thank-you for being early believers.
The overall strategy hasn’t changed — it’s gotten sharper. The Flavors (Essentials, Studio, and the rest) are working as designed. The recipe system handles everything from simple session management to complex multi-persona creative workflows. These just need to be thoroughly tested and simplified so more people can use them confidently.
Some parts of CRAFTFramework.ai may be paused temporarily. Features like the Test Kitchen may be put on hold while I focus on making the fundamentals work extremely well. Better to do the core things brilliantly than to spread thin across everything.
The Bottom Line
CRAFT + Cowork is the combination I’ve been building toward. Cowork gives CRAFT the platform it needed. CRAFT gives Cowork the memory and structure it’s missing. Together, they turn AI collaboration from a series of disconnected conversations into a real, ongoing working relationship.
The Beta isn’t ending — it’s focusing. And I’m more excited about where this is going than I’ve been since day one.
Thanks to all of you for making the CRAFT Beta successful. The best is ahead.
— Richard
Ketelsen Digital Solutions LLC | CRAFTFramework.ai
