Caleb Writes Code — Pi Agent Explained in 6 Minutes

Source: YouTube Channel: Caleb Writes Code (84700 subs) Duration: 6:40 Views: 30690 · Likes: 796 Video: Watch on YouTube

Micro Center is THE AI Destination: https://micro.center/f49d57 Sign up for a FREE 128 gig Flash Drive at Micro Center Austin, TX: https://micro.center/823606 Sign up for a FREE 128 gig Flash Drive at Micro Center Columbus, OH: https://micro.center/f407b5 Visit Micro Center News: https://micro.center/4f8d2c

Pi is one of the most unique harnessing that I’ve seen and it opens doors for so many different ways we can use it like OpenClaw being the prime example.

How does Pi stand up against more frontier agents like Claude Code, Codex, Cursor, and Antigravity as more and more products are being shipped with features that make the harness layer more complex?

Key Insights

Based on the full video transcript:

There are so many coding agents these days, but one of these things is not like the other. And let’s be honest, a lot of them are not only similar in features, they’re actually starting to look like each other. Similar to how most people can’t distinguish Pepsi from Coca-Cola on a blind taste test, coding agents are similar where if I hide the logo from Anti-Gravity, Codex, and Cursor, it’s really hard to tell which one is what. And one agent that stands out is Pye. And a lot of people who use Pye seems to swear by it. So, how does this framework that powers Open Claw stand out against other coding agents that are out there? Welcome to Caleb Wright’s Code, where every second counts. Quick shout-out to Micro-Center, more on them later. Most people probably heard of Pye as the brain that runs Open Claw. But why isn’t Open Claw powered by a much more comprehensive agents like Codex CLI, Gemini CLI, or even Claude Code? Don’t these offer more tools out of the box? What makes Pye unique is more about what an agent isn’t than about what an agent is. It’s kind of like how negative space in art focuses on the empty space around a subject, rather than trying to draw the object itself. Okay, what does all of this mean? Pye is notorious for how much it leaves out instead of how much it adds in. It doesn’t have sub-agents out of the box, it doesn’t have MCP, it doesn’t have background bash, and it doesn’t use to-do list. The real benefit of Pye is when it comes down to its ability to extend its own harness. In conventional coding agents like Claude Code, Codex, and Anti-Gravity, you can’t really change its own harness. Sure, you can configure settings around their harness, but you can’t really extend its own harness. A good example is using hooks. In case you don’t know what a hook is, it’s a mechanism that allows you to interrupt the tool call chain either before or after to perform specific action you want it to do. So, if I wanted to make my agent write an audit trail every time it deletes a folder through a tool call, I can just add a pre-tool use hook to write an audit trail by mechanism. And in the case of Claude code, adding a hook means you’re adding this within the settings.json file for Claude code to parse and consume, all within the predetermined harness. But in the case of Pi, instead of a setting file in JSON, Pi writes an entire TypeScript code as an extension of its own harness natively in code. So the Pi agent actually extends its own harness while being self-aware at the same time. And once I run the {slash} reload command in the terminal, Pi will now incorporate the newly written code as a hook. So you can imagine how this can be used to build applications like Open Claude by building around Pi and adding the scaffolding around it like MCPs, integrations with messaging applications, gateway for hosting, and more. And as you can see, Open Claude can just either import portions of Pi’s components or use the terminal user interface as the module. So then, what exactly is the use cases of Pi? Should people ditch Codex and Claude code and jump into Pi instead? But first, a quick word from Micro Center sponsoring this video. As someone who is working in the AI industry, I really need the right hardware for the job, whether it’s for local inference, fine-tuning, or building my own custom agent here at home. And all these things require parts like GPUs, RAM, CPUs, and storage. Micro Center helps you get the product you need like a list of graphics cards that you can see specifically curated for AI workloads that typically need large amounts of VRAM and fast interconnect. Beyond dedicated graphics cards, I can also shop for solid state drives since most models nowadays need to run as GGUF, which means you need to have a good hard drive to support your locally run inference. For more generic use cases like building agents, I can also shop for Mac Studios or the DGX Spark for a simpler hardware to run everything I need for buildin

Chapters

  • 00:00 — Intro
  • 00:39 — Pi
  • 01:19 — Harness
  • 03:00 — Sponsor: Micro Center
  • 04:04 — Framework
  • 05:23 — Use Cases
  • 06:02 — Conclusion