Pi Coding Agent vs Claude Code vs OpenCode — I Tested All 3
Roman Knox tests Pi — Mario Zechner's deliberately minimal terminal coding agent with only four tools (read, write, edit, bash) — against Claude Code and OpenCode, showing its Copilot OAuth login, forkable JSONL session tree, skill.md and agents.md support, and a 3D Rubik's Cube build that highlights how quiet a no-prompts, no-plan-mode agent feels.
Roman Knox8 minTranscript found
Quick learning frame
Read this before watching.
Coding-agent workflow is the loop of inspect, route, plan, edit, verify, summarize, and decide what should be automated next.
New playlist item from Roman Knox; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to weigh a minimal, own-your-setup coding agent against feature-heavy alternatives by comparing predictability, context handling, and extensibility rather than feature counts.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Inspect context
02Route tool
03Plan work
04Edit safely
05Verify behavior
06Report next step
Deep lesson
Turn this video into working knowledge.
1,495 cleaned transcript words reviewed across 442 timed caption segments.
Thesis
Pi Coding Agent vs Claude Code vs OpenCode — I Tested All 3 teaches a practical coding-agent workflow move: Roman Knox tests Pi — Mario Zechner's deliberately minimal terminal coding agent with only four tools (read, write, edit, bash) — against Claude Code and OpenCode, showing its Copilot OAuth login, forkable JSONL session tree, skill.md and agents.md support, and a 3D Rubik's Cube build that highlights how quiet a no-prompts, no-plan-mode agent feels.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:40
Minimalism as a feature
“own, stripped to the bone, yellow by default, >> >> 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...”
Pi ships with just read, write, edit, and bash — no sub-agents, plan mode, or MCP — because Mario Zechner (of libGDX) was sick of Claude Code's bloat: every added feature made behavior less predictable, silently ate context, and left users touching five of fifty capabilities. List every feature of your current coding agent, mark the ones you actually used this week, and note which of the rest could be silently costing you context.
3:49
Sessions, skills, agents.md
“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...”
Every Pi conversation is a JSONL file you can resume with pi -r or fork from any message into a real non-linear session tree; Pi also reads the same skill.md files as Claude Code (including your ~/.claude folder and a community pi-skills repo installed via pi install), and loads an agents.md from the project root, reloadable with /reload. Write a five-line agents.md for one project (build command, forbidden paths, response style) and practice forking a session to roll back a bad detour.
5:47
The philosophical trade-off
“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...”
Claude Code is a powerful but opinionated 'spaceship' you can't turn off; OpenCode sits in the middle but auto-compacts context aggressively enough to summarize away needed details; Pi never compacts unless told and gives you nothing beyond the basics — sub-agents, LSP, or web search are yours to add via a TypeScript extension API with event hooks. Decide which failure hurts you more — losing context to auto-compaction or wiring up features yourself — and write one paragraph justifying which agent fits your workflow.
01
Inspect context
Start with this video's job: Roman Knox tests Pi — Mario Zechner's deliberately minimal terminal coding agent with only four tools (read, write, edit, bash) — against Claude Code and OpenCode, showing its Copilot OAuth login, forkable JSONL session tree, skill.md and agents.md support, and a 3D Rubik's Cube build that highlights how quiet a no-prompts, no-plan-mode agent feels. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:40, where the video says: “own, stripped to the bone, yellow by default, >> >> 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...”
02
Route tool
Use "Route tool" to locate the part of the coding-agent workflow mechanism the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 3:49, where the video says: “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...”
03
Plan work
Turn "Plan work" into the reusable artifact for this lesson: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal. This is where watching becomes something you can inspect and reuse.
04
Edit safely
Use "Edit safely" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Verify behavior
Use "Verify behavior" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Report next step
Use "Report next step" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed artifact packet
Convert the video into a scoped artifact request that includes the transcript claim, mechanism, acceptance criteria, and proof. The output should be a coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
Example
Coding-agent workflow proof brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the coding-agent workflow pattern.
Example
Teach-back module
Transform the lesson into a definition, a Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
choosing tools by hype
losing context across agents
letting parallel sessions become invisible
Letting the lesson drift into generic Codex vs Claude comparison.
Letting the lesson drift into feature lists without task routing.
Letting the lesson drift into claims that ignore limits or recovery.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: Roman Knox tests Pi — Mario Zechner's deliberately minimal terminal coding agent with only four tools (read, write, edit, bash) — against Claude Code and OpenCode, showing its Copilot OAuth login, forkable JSONL session tree, skill.md and agents.md support, and a 3D Rubik's Cube build that highlights how quiet a no-prompts, no-plan-mode agent feels.
02
Explain the practical stakes without hype: New playlist item from Roman Knox; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: Pi Coding Agent vs Claude Code vs OpenCode — I Tested All 3
- URL: https://www.youtube.com/watch?v=8pfPf8Wmcrc
- Topic: Creative Automation
- My current learning frame: Install Pi from npm, log in through your existing GitHub Copilot subscription with /login, add a short agents.md, then give it one self-contained front-end task (like a single-file three.js demo) and compare the experience against your current agent's prompts and plan-mode friction.
- Why this matters: New playlist item from Roman Knox; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:40 / Evidence 1: "own, stripped to the bone, yellow by default, >> >> 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..."
- 3:49 / Evidence 2: "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..."
- 5:47 / Evidence 3: "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..."
- 7:29 / Evidence 4: "for this one. The link to the docs and the GitHub repo are in the description. Catch you in the next video."
Video-aware target:
- Prompt lane: Coding-agent workflow
- Mechanism to extract: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review.
- Artifact to produce: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
- Artifact must include: task class; agent/tool choice; context packet; verification step; handoff/recovery rule
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step
- answers to these source questions: What workflow pain is being solved? | What exact coordination mechanism is shown? | What evidence proves it changes the work?
- 3 concrete examples that apply the video idea to real agentic work, such as rate-limit routing; browser verification after a UI edit; long-running /goal session review
- 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: choosing tools by hype; losing context across agents; letting parallel sessions become invisible
- a checklist for the next real workflow, focused on: routing decision, context portability, verification, handoff summary
- one practical exercise with a clear done signal: Route three recent tasks across Codex, Claude, browser checks, and manual review with a reason for each.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "Pi Coding Agent vs Claude Code vs OpenCode — I Tested All 3", not a generic Creative Automation essay.
- Each workflow rule must point to a timestamped claim or demo moment, then state what remains unproven.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic Codex vs Claude comparison; feature lists without task routing; claims that ignore limits or recovery.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
Creative AI removes the need for taste.
It increases the need for taste because output volume explodes.
The best prompt is enough.
References, critique, iteration, and post-production matter just as much.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
A reusable artifact with a done signal and one verification step.03
Coding-agent workflow teach-back card
Explain the coding-agent workflow mechanism to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
Which four tools does Pi ship with, and why did Mario Zechner build it that way?
How does Pi's session model differ from most coding agents?
What context-handling difference does the video highlight between OpenCode and Pi?
Source shelf
Use the video as a doorway, then verify with primary sources.
