Agentic AI Systems, Clearly Explained
This video explains agentic AI systems across four levels of complexity: chatbots, AI workflows, agentic workflows, and agentic AI systems. Using content repurposing as a consistent example, the speaker demystifies intimidating terms like harnesses, MCPs, and memory systems, arguing that these systems are fundamentally just files and folders accessible to non-developers.
Summary
The video walks through four progressive levels of AI capability using a single running example — repurposing a YouTube video into social posts, newsletters, and clips — so viewers can feel the difference at each stage.
Level 1 covers chatbots (ChatGPT, Claude, Gemini). The speaker notes that while useful, chatbots are passive and stateless: they don't know your brand, audience, or content history unless you manually paste that context in every time. Projects and Gems offer static context storage, but the AI still waits for prompts and doesn't execute anything autonomously.
Level 2 covers AI workflows (n8n, Zapier, Make.com). These tools automate repetitive pipelines — for example, automatically pulling a transcript, sending it to Claude with a hardcoded prompt, and dropping a draft LinkedIn post into a scheduling tool. The limitation is rigidity: the workflow follows the same steps in the same order every time and cannot make judgment calls, such as recognizing that a topic suits Twitter better than LinkedIn.
Level 3 introduces agentic workflows, which the speaker identifies as the most important conceptual leap. Here, the model — not the human — decides the execution path. Given a high-level goal like 'turn this week's video into content for LinkedIn, Twitter, and my newsletter,' a tool like Claude Code reasons about what to do, acts, observes results, and iterates. This loop is technically called ReAct (Reason and Act). The infrastructure enabling this is called a harness — Claude Code, Codex, and Cursor are all described as harnesses that wrap the model and give it the ability to read files, run commands, and call tools.
Level 4 describes full agentic AI systems: coordinated multi-agent operations where different 'skills' (markdown instruction files) handle specific tasks like clip extraction, carousel creation, newsletter drafting, and ad copy generation. The system loads only the relevant context at the right time to avoid bloating the context window. Memory — which can be as simple as a markdown file — allows the system to carry knowledge across sessions, such as which post formats performed best last month. External tools connect via MCP (Model Context Protocol). Critically, the speaker emphasizes that human-in-the-loop review is a deliberate design principle, not a limitation — nothing gets published without human sign-off. The speaker concludes that despite the intimidating terminology, these systems are essentially organized folders of files, making them accessible to business owners and knowledge workers, not just developers.
Key Insights
- The speaker argues that the critical distinction between AI workflows (Level 2) and agentic workflows (Level 3) is who decides the execution path — in Level 2 the human defines the steps, while in Level 3 the model determines them based on a high-level goal.
- The speaker defines a 'harness' as the infrastructure surrounding a model — such as Claude Code, Codex, or Cursor — that turns thinking into doing by giving the model access to files, the ability to run commands, and connections to external tools, distinguishing it from a browser-based chatbot.
- The speaker claims that 'skills' in a Level 4 agentic system are simply markdown files containing instructions for specific tasks, and that the agent loads only the relevant skill and reference examples when needed to avoid bloating the context window and wasting tokens.
- The speaker asserts that memory in agentic AI systems can be as simple as a markdown file the system reads and updates between sessions, allowing it to remember things like which post formats performed best last month rather than starting from zero every time.
- The speaker states they have not yet encountered a system powerful enough to bypass the human-in-the-loop review stage, and that the best real-world agentic systems are deliberately designed with human review built in at either the input or output stage before anything goes live.
Topics
Transcript
[0:00] I can't hear another word about agents. >> This is the next big step forward. A full coding agent. Every single software company in the world needs an agentic systems. >> I mean agents is it's almost sort of a buzz word, right? Like everybody you talk to now is building agents. >> Agentic coding experience. Do a complicated coding agentic thing. >> Codex is another sort of agent app. >> What is an agent? >> Agent agentic harness. >> All right. Most explanations of agentic AI systems are either too technical or too basic. So this one's meant for people like me. You're not a developer. [0:30] You use chat or claude every single day. You've probably open…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Simon Scrapes
I Rebuilt Hermes in Claude Code (It’s Ridiculously Good)
The creator rebuilds key features of the Hermes agentic AI system inside their own Claude Code setup rather than installing it off-the-shelf, arguing that understanding the architecture provides more long-term leverage. They identify three hidden costs of pre-built systems: inherited assumptions, inability to fix unknown code, and poor scalability. Their custom build addresses Hermes's limitations in multi-client identity management, semantic memory recall, and skill system maintainability.
Stop Downloading Claude Code Skills. Do This Instead.
The video argues that downloaded Claude Code skills are too isolated or bloated to drive real business outcomes. The speaker introduces 'skill systems' — orchestrated chains of small, focused skills that feed into each other end-to-end. A practical example shows a five-skill automation that converts a YouTube video into five ready-to-post short-form clips.
Master 80% of Claude Code, Just Learn These 15 Things
This tutorial covers 15 foundational concepts for using Claude Code effectively, emphasizing that context management is the single most critical skill. The presenter draws from real user behavior across thousands of users to show how plan mode, context tools, slash commands, skills, hooks, MCPs, and memory systems combine to form a powerful agentic workflow.
Master Claude Design in One Video (Complete Build)
The video demonstrates a live build using Claude Design to create real business assets for the Aentic Academy, including a landing page, mobile wireframe, and slide deck. The host emphasizes that building a proper design system upfront is the single most important factor in avoiding generic AI aesthetics. The video compares multiple methods: using ChatGPT's image model, the Skill UI CLI tool, and Claude Design's native interface.
Claude just got another superpower (but they kept it quiet!)
A creator discovers buried features in a recent Claude desktop app update, including file system visibility, split-view sessions, and markdown rendering. These changes make the desktop app a viable replacement for terminal-based Claude Code workflows. The creator argues this enables structured, context-aware agentic project management without needing VS Code or a terminal.