OpenCode Go + CodeGraph: Can Cheap Models Do the Job?
This video tests whether inexpensive OpenCode Go models can build an automatic, face-centered picture-in-picture feature and whether CodeGraph reduces their token use. CodeGraph's effect varies sharply by model, while independent visual checks uncover a bug in every completed implementation despite all six passing their automated suites.
The Gray Cat10 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 The Gray Cat; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to evaluate coding-agent tools by comparing controlled runs, stage-level token use, independent product checks, and the actual usability of the resulting feature.
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,427 cleaned transcript words reviewed across 434 timed caption segments.
Thesis
OpenCode Go + CodeGraph: Can Cheap Models Do the Job? teaches a practical coding-agent workflow move: This video tests whether inexpensive OpenCode Go models can build an automatic, face-centered picture-in-picture feature and whether CodeGraph reduces their token use. CodeGraph's effect varies sharply by model, while independent visual checks uncover a bug in every completed implementation despite all six passing their automated suites.
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:35
Specify Real Constraints
“hitting the limits. I'll show you which models use fewer tokens and whether the code was worth keeping. The task was another feature for The Gray Cat, my video editing app. It already picks screencasts to match what...”
The requested feature must detect and center a face, choose a stable crop across a recording, stay synchronized when screencasts are sped up, add a rounded white border, and remain easy to edit in Premiere. Those workflow constraints make the task more revealing than simply asking a model to render a small video overlay. Rewrite one feature request as a checklist covering content detection, temporal stability, synchronization, visual treatment, and the downstream editing workflow.
2:28
Control The Comparison
“wrote the code themselves. They didn't delegate work to other agents. The $10 only covered OpenCode Go. Claude wasn't included in that. But, Go has usage limits for 5-hour periods. There are weekly and monthly caps, too. Kimiko...”
Each model starts from its own copy of the same code and task, runs once with CodeGraph and once without it, and receives the same supervised plan review, code review, and single repair chance. Subscription limits prevent some models from finishing, illustrating why quota failures must be separated from evidence about implementation quality. Design an A/B agent test with identical repository copies, prompt, review gates, repair allowance, and completion criteria, then record quota failures separately from code-quality results.
6:28
Passing Is Not Ready
“input that wasn't cached. That costs more than reading cached text. DeepSeek was free in these runs. Those amounts show what the recorded usage would cost at those rates. They weren't extra subscription charges. Astra recommended the code...”
CodeGraph saves 39% of MiniMax's tokens and about 10% of DeepSeek's, but nearly doubles Muse Spark's usage; one run per condition is not enough to treat those differences as stable. More importantly, every completed version passes its automated tests while separate checks still reveal visible or state-related bugs, including an inverted preview, a misplaced mask, and a stale face crop. Add one independent visual check and one state-change check to an agent-built feature, then compare their findings with the automated suite before deciding whether to keep the code.
01
Inspect context
Start with this video's job: This video tests whether inexpensive OpenCode Go models can build an automatic, face-centered picture-in-picture feature and whether CodeGraph reduces their token use. CodeGraph's effect varies sharply by model, while independent visual checks uncover a bug in every completed implementation despite all six passing their automated suites. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:35, where the video says: “hitting the limits. I'll show you which models use fewer tokens and whether the code was worth keeping. The task was another feature for The Gray Cat, my video editing app. It already picks screencasts to match what...”
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 2:28, where the video says: “wrote the code themselves. They didn't delegate work to other agents. The $10 only covered OpenCode Go. Claude wasn't included in that. But, Go has usage limits for 5-hour periods. There are weekly and monthly caps, too. Kimiko...”
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: This video tests whether inexpensive OpenCode Go models can build an automatic, face-centered picture-in-picture feature and whether CodeGraph reduces their token use. CodeGraph's effect varies sharply by model, while independent visual checks uncover a bug in every completed implementation despite all six passing their automated suites.
02
Explain the practical stakes without hype: New playlist item from The Gray Cat; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Brief -> Source material -> Generation -> Selection -> Edit -> Taste review -> Reusable recipe sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A creative production board with source inputs, prompt recipe, selection criteria, edit pass, and taste-review checkpoints.
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: OpenCode Go + CodeGraph: Can Cheap Models Do the Job?
- URL: https://www.youtube.com/watch?v=blS3l32vBR0
- Topic: Creative Automation
- My current learning frame: Run a controlled with-versus-without tool comparison on one small feature, break token usage down by planning, implementation, and repair, and finish with independent visual and state-change tests before judging the winning attempt.
- Why this matters: New playlist item from The Gray Cat; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:35 / Evidence 1: "hitting the limits. I'll show you which models use fewer tokens and whether the code was worth keeping. The task was another feature for The Gray Cat, my video editing app. It already picks screencasts to match what..."
- 2:28 / Evidence 2: "wrote the code themselves. They didn't delegate work to other agents. The $10 only covered OpenCode Go. Claude wasn't included in that. But, Go has usage limits for 5-hour periods. There are weekly and monthly caps, too. Kimiko..."
- 4:09 / Evidence 3: "price. Code graph helps a model find related code. For example, it can show which functions call the function being changed. Muse used code graph 14 times while working on its plan. And that planning actually used slightly..."
- 6:28 / Evidence 4: "input that wasn't cached. That costs more than reading cached text. DeepSeek was free in these runs. Those amounts show what the recorded usage would cost at those rates. They weren't extra subscription charges. Astra recommended the code..."
- 9:39 / Evidence 5: "it before it could finish. Super models might help with simple tasks if the plan is detailed enough. I'd still check their work. For my earlier graph file and code graph comparison, watch 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 "OpenCode Go + CodeGraph: Can Cheap Models Do the Job?", 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.
What made automatic face framing harder than placing a fixed picture-in-picture window?
How were the CodeGraph and non-CodeGraph attempts kept comparable?
What did the separate checks reveal that the automated suites did not?
Source shelf
Use the video as a doorway, then verify with primary sources.
