The bait, then the rug-pull.
Twenty-two tools. One custom OS. Built entirely in Claude Code, deployed on a self-improving agent hierarchy that adds features while the creator sleeps. Marcelo walks through every module of ClearMud OS live, including the two-model YouTube script pipeline that uses Opus for research and Sonnet for writing, and the Content Cascade that handles repurposing automatically twelve hours after upload.
What the video promised.
stated at 00:13“Today I am gonna show you the entire system that I built from the inside.”delivered at 00:22
Where the time goes.

01 · Hook + OS intro
Claim-stack hook naming 5 outputs, immediate screen share of ClearMud OS dashboard with live channel stats. Autonomous tabs built overnight by agents are highlighted.

02 · Content Calendar
Kanban + calendar view replacing Notion. Drag-and-drop, one-click script-to-calendar automation, teleprompter the agent built unsolicited.

03 · Research tab
Reddit + X scraping for topic validation, inspired by Greg Eisenberg / Matt Van Horn Last 30 Days tool. Key themes and suggested video angles.

04 · Generate Ideas + Idea Bank
Paddy Galloway methodology baked in. Scores ideas, gives thumbnail concept + hook. Idea Bank holds 10+ daily ideas. One click sends any to YouTube Script.

05 · YouTube Script tool (overview)
Most-used tool. Title/thumbnail/hook methodology compiled from Paddy Galloway, Colin and Samir, Alex Finn. Two-turn model split: Opus researches, Sonnet writes.

06 · Video to Social
Paste YouTube URL, get LinkedIn, X, Substack, blog copy in voice pulled from transcript. No predefined voice DNA needed.

07 · Live Streams tool
Transcript in, timestamps + optimized YT description out. Automation in progress: agent will run 48hr post-livestream and fill YT dashboard fields.

08 · Copywriter + Prompt Library
Newsletter, blog, Substack under Gary CMO agent. Prompt Library was agent-built without being asked, in prep for newsletter launch.

09 · Optimize + Content Cascade + Sponsor Hub + Growth
Title Lab for A/B testing. Content Cascade pipeline monitor: Hype agent posts 12hr after upload. Sponsor Hub and Growth roadmap both agent-built and blurred.

10 · Notes, Files, Documentation, Settings
Sticky notes by project, Files browser, auto-versioned docs with HTML architecture diagram, brand kit with avatar marks for image gen.

11 · YouTube Script live demo
Live run: types topic, Turn 1 fires Opus (trend analysis + 3 strategies), picks strategy, Turn 2 fires Sonnet (full script). One click adds to Calendar.
Visual structure at a glance.
Named ideas worth stealing.
Two-Model Split
- Opus 4.6 for research and strategy selection
- Sonnet for script execution
Split expensive model for analytical tasks, cheaper model for execution. Works because methodology in the commands handles the quality gap.
Agent Hierarchy (CMO Model)
- Muddy (main agent)
- Gary Vaynerchuk (CMO sub-agent)
- Rex (YouTube script)
- Hype (social copy)
Main agent delegates to domain-specific sub-agents who act autonomously within their scope. Mirrors a real media company org chart.
Single ROI Metric
- Time is the only ROI metric tracked
Every tool built is evaluated solely by how much time it frees up. Cuts feature creep and prioritization noise.
Overnight Self-Improvement Loop
- Agents build one new feature on ClearMud OS per night
- Agents build one new feature on Muddy OS per night
- No prompting required
Feed agents enough context about your goals and they build toward those goals autonomously during off-hours.
Weekday/Weekend Split
- Weekday: operate (create, edit, post, stream)
- Weekend: infra day (8-10 hrs improving agents)
Separates creation mode from building mode. Avoids context-switching penalty during the week.
Lines you could clip.
“You are gonna notice something with everything I build. I build things that focus on one ROI metric only, and that is time.”
“I enjoy coming up with ideas. I enjoy the ideation process. I enjoy making thumbnails, believe it or not. So I have built all of these tools to free up my time to focus on what I enjoy doing the most.”
“This was not a one shot. This is well over a hundred hours of work and iteration and sleepless nights.”
“I am not an AI expert. I am building in public and sharing what actually works.”
How they spent the runtime.
Things they pointed at.
How they asked for the click.
“Drop a comment below. Let me know what you are building. Let me know what this has inspired you to build.”
Comment engagement CTA plus personalized video request offer. No subscribe push, no sponsorship.
Word for word.
Build the OS, not just the tool.
Every piece Marcelo built solves exactly one pain point — the compounding comes from wiring them all together under one UI with shared agents.
- Use the two-model split: Opus or best model only for research and strategy, Sonnet for execution. Same or better output at lower cost.
- Give your main agent a goals document with channel context and short/medium/long-term targets. It starts building toward those goals autonomously overnight.
- Wire a Content Cascade: one long-form upload should auto-trigger blog post, social copy, and cross-post via a sub-agent on a 12-hour delay.
- Structure sub-agents by function (CMO, script writer, social poster) not by task. Each agent owns a domain, reports up, acts freely within it.
- Block one day per week as infra day. Weekday = operate. Weekend = improve the agents. Never mix the two.
- Build the teleprompter even if you think you will not use it. The agent-built features you did not ask for often become the ones you use most.
Your time is the only budget that matters.
Every tool Marcelo built was measured by a single question: how many hours does this free up? That question will cut more scope creep than any prioritization framework.
- Pick one task you repeat every week and calculate the actual time cost of doing it manually.
- You do not need to build a full OS. One automated pipeline (idea to script, or video to social post) compounds fast.
- Keep the parts you enjoy. Automation should free you for your best work, not replace it entirely.
- The overnight self-improvement loop works because Marcelo gave his agents rich context about his goals. Quality of output scales with quality of context you put in.





































































