Pi is INCREDIBLE - Building a Custom Coding Agent Live

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: Pi is INCREDIBLE - Building a Custom Coding Agent Live
- URL: https://www.youtube.com/watch?v=lK9o5Wu2upU
- Topic: Agent Architecture
- My current learning frame: Install Pi, switch its default model to a cheap provider via models.json, add the web-access and permission-gate extensions, then run a small coding task and compare its quality and speed against your usual Opus/Claude Code setup.
- Why this matters: New playlist item from Cole Medin; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:14 / Evidence 1: "other coding agents right now. And so, the idea behind Pi is it is a minimal coding agent. It's made to be a coding agent that you build on top of instead of taking a really massive bloated..."
- 7:00 / Evidence 2: "great because it really is this minimal agent that allows us to use any model we could possibly dream of. Like we can use Kimmy K 2.6 for example, like I'll use in the stream today. But then..."
- 26:40 / Evidence 3: "factory. Curious how pi could help. So the the reason pi could be really helpful for the dark factory is because I have a very specific workflow for the way that I have the coding agent evolve the..."
- 28:12 / Evidence 4: "Okay. Um, Jcode. Sure. So I they Okay. So you can see that Pi is the second best, but apparently J-code is better with local embeddings off. I don't care that much about speed. Like here, here's the..."
- 49:01 / Evidence 5: "and rules and things like that, but it's like fundamentally even the coding agent itself, how it operates with the core loop, the core while loop of the agent. Like even that you can change. You can tweak..."
- 71:51 / Evidence 6: "really neat. The Codeex app specifically how you can manage your different projects and parallel agents and like the updates from there. It's kind of like the agent view that Claude Code released where you can see all..."
- 87:25 / Evidence 7: "extension so that the output of like the the last output from the workflow needs to go directly back into the the PI session I thought that's what you already had set up, but obviously not. It's very..."

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, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A one-page agent harness map with tool boundaries and proof signals.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Model -> Harness -> Tools -> Verifier -> Artifact
   - 3 concrete examples that apply the video idea to real agentic work
   - 2 failure modes the video helps prevent
   - a checklist I can use the next time I run Codex or Claude
   - one practical exercise with a clear done signal
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 is INCREDIBLE - Building a Custom Coding Agent Live", not a generic Agent Architecture essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.