Pi Coding Agent demonstrates that a minimalist approach with only four tools (read, write, edit, bash) and a sub-1000 token system prompt can outperform more complex AI coding agents like Claude Code, which suffer from unpredictable behavior, bloated features, and context consumption issues. The key insight is that reducing functionality increases predictability and reliability, as fewer features mean fewer points of failure and less cognitive overhead for users.
Deep Dive
Prerequisite Knowledge
- No data available.
Where to go next
- No data available.
Deep Dive
Pi Coding Agent vs Claude Code vs OpenCode — I Tested All 3Added:
Pi is one of those rare tools that gets popular by doing less. It's a coding agent built by Mario Zechner, the same guy behind GDX library. And what's interesting is the fastest growing terminal coding agent right now is not the one with sub agents, plan mode, or fancy MCP integrations. It's this minimal little thing that ships with only four tools: read, write, edit, and bash. That's it. Mario built it because he was sick of Claude code becoming bloated. He noticed something a lot of us felt but didn't really say out loud.
Every new feature added to these big agents made the behavior less predictable. Bugs piled [music] up, context got eaten silently, and you'd end up with a tool that does 50 things but you only use five of them. So, instead of fighting it, he built his own, stripped to the bone, yellow by default, >> [music] >> no permission prompts, no background bash, no swarm of sub agents, just the model and a tiny harness around it. And honestly, I didn't think I'd switch.
I've been on open code for a while. I had my templates, my sub agents, my whole setup. But after running Pi for a couple of weeks, I'm not going back. So, let me start with installation. Pi is on NPM, so one command and you are done.
You type Pi, hit enter, and you're [music] in. The first thing you'll notice is the interface is small, like really small. There's no banner, no ASCII art, no login wall blocking you, just a prompt [music] and a footer telling you the model, the working directory, and the token usage. That's the whole UI. Now, for the provider part, this is where it gets fun. Pi supports almost everything: Anthropic, OpenAI, Google, DeepSeek, Cerebrus, Grok, OpenRouter, Bedrock, Azure, Versal AI Gateway, even local stuff like Ollama or LM Studio. But the one I want to use today is GitHub Copilot. A lot of us already pay for Copilot Pro or have it through work. So, why not get more out of it? Pi can route your request through your existing Copilot subscription, which means you can use models like GPT-5.1, Claude Sonnet, or Gemini without paying extra. Setup is simple. Inside Pi, you type {slash} login. A list shows up with the providers that support OAuth. Pick GitHub Copilot. It asks you to press enter for github.com or type a Copilot Enterprise domain if your company uses one. Most of you will just hit enter. It opens your browser, you authorize, and you're back in the terminal. The token is saved and Pi will refresh it automatically when it expires. After login, I run /model or hit control L to switch. I'll pick Claude Sonnet through Copilot for this test. [music] The footer at the bottom updates and shows the active model. From here, anything I type just goes to the model. Every conversation is saved as a JSONL file.
You can resume any session with pi -r and pick from a [music] list. You can also fork a session at any point. So, if I made a side trip into something dumb and want to roll back without losing my main thread, I just fork from the message I want and branch off.
>> [music] >> The session tree is real. It's not linear like most other agents. This is huge for keeping the context clean. The second thing is skills. Pi reads skill.md files just like Claude Code does. So, if you already have skills set up in your tilde /.cloud folder, Pi finds them. Same with project level skills. They show up at startup in the header. There's also a community skills repo called Pi skills with stuff like a babysitter skill that double-checks the agent's work, a sub-agent skill, and others. To install one, you do pi install and the path. That's the whole thing. The third [music] is the agents.md file. You drop one in your project root and Pi loads it as context.
I keep mine short. Things like run npm, run check after edits, do not touch migrations, keep responses tight, whatever rules I want. If I change the file, I run /reload and it picks up the new version. There's also bash escape.
If I just want to run a quick shell command without leaving the agent, I type an exclamation mark and the command like exclamation mark git status. It runs and shows the output in line. And if I want to edit my prompt in a real editor instead of the terminal box, control G opens it in my system editor.
Small thing, but I use it constantly, okay? Now, the actual test. I want to see how Pi performs on a creative front-end task with a Copilot model behind it. So, my prompt is going to be straightforward. I'm going to tell it to build a 3D Rubik's Cube using three.js in a single HTML file. It needs to be interactive. You should be able to click and drag to rotate the whole cube, and the faces should be turnable with mouse drags, too. [music] Keep it self-contained, no build step. I want to open the file in a browser and have it work. I paste the prompt in. Pi starts thinking. The thinking indicator shows in the editor border, which I find kind of nice because it's not in your face.
It reads the directory first using ls, [music] sees there's nothing there, and then starts writing. The bash tool is what it uses [music] to actually create the file. It pipes the HTML content through cat [music] and writes it to disk. No fancy file edit tool needed for a fresh file.
>> [music] >> You can see how minimal the loop is. The model decides what tool Pi runs it. The output comes back, and the loop continues. After about 90 seconds, it [music] finishes. The file is on disk. I open it in Chrome. There's a black canvas with a 3x3 Rubik's Cube floating in the middle, six colors, white on [music] top, yellow on bottom, red, orange, blue, green on the sides. I drag with my mouse, and the whole [music] cube spins smooth. Then I click on a face and try to drag a row, and it actually rotates a single [music] layer.
The animation is decent, not perfect.
The rotation snaps back to a 90° multiple when I let go, which is exactly what you'd want. What I want to highlight here is not that the cube works. [music] Plenty of agents could build that. What I want to highlight is how quiet the experience was. [music] No pop-ups asking me to approve every bash command. No plan mode making me confirm a 10-step roadmap before writing a single line. No sub-agent spinning up another model to second-guess the first.
Just a model, a few tools, and a clean session file I can fork later if I want to try a different approach. If I compare this to Claude Code, the difference is mostly philosophical.
Claude Code has hooks, plan mode, MCP servers, skills, sub-agents, [music] the whole spaceship. It's powerful, but it's also opinionated, and you can't really turn most of it off. Open Code sits in the middle. It has LSP support, an SST-style design, and decent extensibility. But, it auto compacts your context aggressively, and that has bitten me on long sessions where it summarized away things I needed. Py just doesn't compact unless you tell it to.
Your session is your session. Now, there's a trade-off. Py gives you nothing out of the box beyond the basics. If you want a sub-agent system, you bring it. If you want LSP feedback, you write an extension or use a skill.
If you want web search, you wire it up.
[music] The good news is the extension API is basically just TypeScript with event hooks. Session start, tool call, tool result, message added, [music] you write a few lines, drop it in tilde slash dot py slash agent [music] slash extensions, and it loads. Peter Steinberger built Open Claw on top of it. The fastest-growing [music] thing on GitHub right now in this space is built on Py, and the reason is the same reason I'm sticking with it. [music] Less stuff means less to break. So, would I recommend it to you? If you like fiddling, [music] yes. If you want a polished out-of-the-box experience with planning, sub-agents, and a bunch of integrations pre-installed, probably not. Py is for people who want to own their setup. If that sounds like you, install it tonight, hook up your Copilot subscription, write a small agent.md, and just see how it feels. You can always go back to Claude Code or Open Code if it's not for you. But, I think a lot of you are going to stay. That's it for this one. The link to the docs and the GitHub repo are in the description.
[music] Catch you in the next video.
Related Videos
OpenHuman VS Hermes AI: Who Wins?
JulianGoldieSEO
285 views•2026-05-29
Long-Running Agents — Build an Agent That Never Forgets with Google ADK
suryakunju
142 views•2026-05-30
5 Mind Blowing Omni Uses Cases
PaulJLipsky
1K views•2026-06-02
This computer is made from real human brain cells. And you can buy it.
Talktmsmedia
3K views•2026-05-28
BREAKING: Microsoft’s New Image Generating Model Beat Out GPT 1.5 and Nano Banana 2
aimmediahouse
122 views•2026-06-03
I Made the Same Anime Fight Scene in Every AI Video Generator
NobleGooseAnime
295 views•2026-05-30
Nvidia Bets Big On AI PCs | New Chip To Power Windows Laptops | Technology | AI Updates | N18S
cnnnews18
3K views•2026-06-01
I Tested NEW Opus 4.8 on Four Projects (Updated LLM Leaderboard)
AICodingDaily
298 views•2026-05-29











