This video tears down OpenCode, the 180,000-star open source terminal coding agent, showing how its bring-your-own-model design (free models, GLM 5.2, DeepSeek, plus Google/Anthropic/OpenAI via models.dev) and custom agent system stack up against Claude Code on features and real cost.
Better Stack7 minTranscript found
Quick learning frame
Read this before watching.
Coding-agent workflow is the loop of inspect, plan, edit, verify, summarize, and route the next task to the right tool.
New playlist item from Better Stack; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to set up OpenCode with the right models and custom primary/sub agents for your workflow, and to judge when its open source, multi-model approach actually beats Claude Code on cost versus when a subscription plan wins.
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
02Plan
03Edit
04Verify
05Review
06Route
Deep lesson
Turn this video into working knowledge.
1,378 cleaned transcript words reviewed across 396 timed caption segments.
Thesis
Open Source Is Back. Goodbye Claude. teaches a practical codex + claude workflows move: This video tears down OpenCode, the 180,000-star open source terminal coding agent, showing how its bring-your-own-model design (free models, GLM 5.2, DeepSeek, plus Google/Anthropic/OpenAI via models.dev) and custom agent system stack up against Claude Code on features and real cost.
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:00
Bring your own models
“Open code is an open source coding agent that just crossed 180,000 stars on GitHub and it's a direct replacement for tools like Claude code without the glitchy UI and expensive subscriptions. You'll get access to hundreds of...”
OpenCode ships the same core tools that made Claude Code useful (bash, edit, grep, web fetch, web search) but lets you swap models freely via /models and the models.dev directory, so cheap options like GLM 5.2, which beat Anthropic's frontier model at web design on Design Arena, can replace expensive API-only pricing. Install OpenCode, run the /models command, and switch between a free default model and GLM 5.2 on the same small task to compare output quality and cost.
2:04
Primary vs sub agents
“model. Then call on those for specific tasks. And this is a great way to segue into configuring Open Code's agents. In Open Code, agents come in two types, primary and sub agents. Primary are the top-level agents...”
OpenCode has no auto model-routing like Copilot, so the workaround is agents: primary agents (build and plan, switched with tab or /agents) drive top-level work, while sub agents like general and explore handle specialist tasks and can be tagged manually with the @ character. In OpenCode, plan a small feature with the plan agent, switch to build to implement it, then invoke the explore agent with @ to answer a question about your codebase read-only.
4:37
Custom agents and cost verdict
“guide your agent in the correct direction. So, next time that you trigger a prompt that requires design work, it's going to do exactly what you want. So, here as another example, we have review.md, and this will...”
Custom agents live either in the central JSON config or as markdown files in .opencode/agents (e.g. a UI engineer on GLM 5.2 with high temperature, a code reviewer on Claude Sonnet 4 with near-zero temperature and preset permissions); on cost, OpenCode wins on API-only pricing, but Anthropic blocks Pro/Max subscriptions from third-party harnesses, so subscribers get a bigger discount staying on Claude Code. Write one sub-agent markdown file (description, mode, model, temperature, permissions, and detailed instructions) for a task you repeat weekly, then trigger it with @ on a real prompt.
01
Inspect
Start with this video's job: This video tears down OpenCode, the 180,000-star open source terminal coding agent, showing how its bring-your-own-model design (free models, GLM 5.2, DeepSeek, plus Google/Anthropic/OpenAI via models.dev) and custom agent system stack up against Claude Code on features and real cost. Treat "Inspect" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “Open code is an open source coding agent that just crossed 180,000 stars on GitHub and it's a direct replacement for tools like Claude code without the glitchy UI and expensive subscriptions. You'll get access to hundreds of...”
02
Plan
Use "Plan" to locate the part of the codex + claude workflows workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 2:04, where the video says: “model. Then call on those for specific tasks. And this is a great way to segue into configuring Open Code's agents. In Open Code, agents come in two types, primary and sub agents. Primary are the top-level agents...”
03
Edit
Turn "Edit" into the reusable artifact for this lesson: A routing matrix for when to use Codex, Claude, browser checks, or manual review. This is where watching becomes something you can inspect and reuse.
04
Verify
Use "Verify" 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
Review
Use "Review" 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
Route
Use "Route" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a routing matrix for when to use codex, claude, browser checks, or manual review..
Example
Claim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
Example
Teach-back module
Transform the lesson into a definition, a mechanism 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.
Letting the prompt drift into generic advice that could apply to any video in the playlist.
Copying the tool setup without identifying the operating principle that transfers to your own stack.
Skipping the artifact, which means the learning never becomes operational or inspectable.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: This video tears down OpenCode, the 180,000-star open source terminal coding agent, showing how its bring-your-own-model design (free models, GLM 5.2, DeepSeek, plus Google/Anthropic/OpenAI via models.dev) and custom agent system stack up against Claude Code on features and real cost.
02
Explain the practical stakes without hype: New playlist item from Better Stack; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect -> Plan -> Edit -> Verify -> Review -> Route sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
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: Open Source Is Back. Goodbye Claude.
- URL: https://www.youtube.com/watch?v=wOfm7x0i3sw
- Topic: Codex + Claude Workflows
- My current learning frame: Install OpenCode, configure two custom sub agents with different models and temperatures (one for UI work, one for code review), run a small feature through plan-then-build, and tally what the session would have cost on your current Claude setup versus the cheaper models.
- Why this matters: New playlist item from Better Stack; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:00 / Evidence 1: "Open code is an open source coding agent that just crossed 180,000 stars on GitHub and it's a direct replacement for tools like Claude code without the glitchy UI and expensive subscriptions. You'll get access to hundreds of..."
- 2:04 / Evidence 2: "model. Then call on those for specific tasks. And this is a great way to segue into configuring Open Code's agents. In Open Code, agents come in two types, primary and sub agents. Primary are the top-level agents..."
- 4:37 / Evidence 3: "guide your agent in the correct direction. So, next time that you trigger a prompt that requires design work, it's going to do exactly what you want. So, here as another example, we have review.md, and this will..."
- 6:24 / Evidence 4: "Anthropic's Pro or Max plan, for example, you cannot use third-party harnesses like Open Code because Anthropic specifically block access to them. But, if you are on that subscription, then Claude Code bundles in a huge discounts compared..."
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 "Open Source Is Back. Goodbye Claude.", 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.
Misconceptions
What to stop believing.
One agent should do every task.
Different tools have different strengths. Routing is part of the workflow.
More context is always better.
Relevant context helps; stale context causes drift and cost.
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 routing matrix for when to use codex, claude, browser checks, or manual review..
A reusable artifact with a done signal and one verification step.03
Teach-back card
Explain the lesson 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.
What advantages does OpenCode offer over Claude Code according to the video?
How do primary agents and sub agents differ in OpenCode?
When does Claude Code still win on cost over OpenCode?
Source shelf
Use the video as a doorway, then verify with primary sources.
