Every month, I ask members to send me the problems they are stuck on, the AI tools they are not sure about, or the workflows they want me to think through live. This session had around 12 reader questions, and the interesting part was that most of them were really asking the same deeper thing:
“How do I stop jumping between scattered AI tools and build one repeatable setup I can actually use?”
That showed up in a bunch of different forms:
Claude Chat vs Claude Cowork vs Claude Code
Codex vs Claude Code
MCP vs CLI
Supabase vs local Markdown files
Tavily vs Geonode
Paperclip vs Hermes vs n8n
How to make AI write in your own voice
How to turn RSS feeds and newsletters into article ideas
Different questions, same pressure.
This is something I’ve been noticing with some of my clients, people in Agentic Academy, as well as founding members: most of them want the same thing, which is to build an AI system that connects across their work so they no longer need to jump between multiple AI tools, because it’s just so tiring and ineffective.
This Q&A helped me explain how I think about that right now. The answer I kept coming back to was simple: pick a main work layer, teach it your real files, and only add tools when they solve a workflow you actually have.
If you read through the full Q&A, you will see that idea from a few different angles:
Benjamin’s question shows how I think about one main AI work layer.
Kurt’s questions show why source material and writing rules matter more than asking for a better prompt.
Lee’s question gets into why I am moving some workflows from MCP to CLI and Skills
Will’s Supabase question shows when a local folder is enough
Mynders’ research question shows how raw information becomes useful only when it connects back to the work.
And the Codex’s new Record and Replay feature demo at the end shows how you can build a skill by letting AI record and see your screen.
This whole session is a look at how I decide what belongs in the system, what can stay simple, and what is worth turning into something reusable.
I am still refining this monthly Q&A format, so I would love your feedback at the end: more Q&A, more live demos, tool reviews, workflow teardowns, or member build reviews.
Benjamin: “How do I build clean architecture across Claude Chat, Cowork, Code, Notion Agents, Skills, MCP, and my SOPs?”
Benjamin’s question was the perfect starting point because it named the whole problem.
He was trying to figure out how to create a clean setup across Claude Chat, Claude Cowork, Claude Code, Notion Agents, Skills, MCP, and his own SOPs. My read was that he had projects spread across multiple places and wanted them to talk to each other without constantly jumping around.
I get this because I used to have a similar mess. I had chat projects. I had code projects. I had different AI surfaces for different jobs. It worked, but it created mental overhead every time I had to decide where the work should happen.
My answer now is pretty direct: I use Claude Code and Codex as my main work layers.
I do not use Claude Chat much anymore, except for quick mobile help when I am traveling or need a fast answer away from my computer. For real work, I want the agent inside the folder where the files already live.
Inside my Claude Code setup, I have:
