The Complete Beginner’s Guide to Open Source Models (2026)

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

Source video:
- Title: The Complete Beginner’s Guide to Open Source Models (2026)
- URL: https://www.youtube.com/watch?v=InhUSQZA7n8
- Topic: Codex + Claude Workflows
- My current learning frame: Set up OpenCode with an OpenRouter key, enable two open-weight models, and build the same small React app with each in separate directories, logging tool-call errors, server behavior, and cost per key to pick your default.
- Why this matters: New playlist item from James NoCode; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:00 / Evidence 1: "Now, I've been using commercial LLMs for agentic coding tasks for a long time, but in the last several months, I've been using more and more of the open weight LLMs to augment my workflow. And especially in..."
- 2:23 / Evidence 2: "directly. You're going to be interacting with something called a local coding agent or a harness, as it's also called. And in this example, I'm using Open Code, but there's lots of harnesses. So, something like Code Rex,..."
- 5:50 / Evidence 3: "workflow and get to work building apps. Now, the first piece that I want to talk about is our local coding agent or the harness. And this is where I prefer using open code. And so, if you..."
- 10:30 / Evidence 4: "build our apps. Now, back in open code, what you want to do is you want to click on new session right here. As you can see, I have a brand new session. And then what you want..."
- 13:55 / Evidence 5: "configured the provider in Open Code and we've also configured the models in that provider so that they show up here for easy switching, easy config. We are ready to start building our apps. And what we're going..."
- 18:52 / Evidence 6: "models do compared to our kind of baseline DeepSeek build here. And so I'm going to go back to Open Code, and I'm going to go ahead and create a new session. And so next we're going to..."
- 27:16 / Evidence 7: "these are minor issues. Remaining limitations. Ticket data is static and local only, etc. etc. But now I want to go ahead and run the last app build. And this is where we're going to be using the..."

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 routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
   - 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 "The Complete Beginner’s Guide to Open Source Models (2026)", not a generic Codex + Claude Workflows 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.