A hands-on walkthrough of downloading and running a new self-improving open-source coding model family (9B, 31B, 35B MoE, and 397B MoE variants) locally on a Mac using MLX and OllamaX, then stress-testing it against Qwen 3.5 with real email-writing, code-base, Webflow MCP, and front-end generation tasks.
Samuel Gregory14 minTranscript found
Quick learning frame
Read this before watching.
Creative automation uses agents to accelerate production while keeping human taste in story, pacing, selection, and critique.
New playlist item from Samuel Gregory; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to pick the right local model size for a task and actually run and benchmark it on your own Mac using MLX/OllamaX, judging its real coding and agentic performance rather than trusting benchmark charts.
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.
01Brief
02Source
03Generation
04Selection
05Edit
06Taste Review
Deep lesson
Turn this video into working knowledge.
2,257 cleaned transcript words reviewed across 690 timed caption segments.
Thesis
Can This New Local AI Model Beat Qwen? teaches a practical creative automation move: A hands-on walkthrough of downloading and running a new self-improving open-source coding model family (9B, 31B, 35B MoE, and 397B MoE variants) locally on a Mac using MLX and OllamaX, then stress-testing it against Qwen 3.5 with real email-writing, code-base, Webflow MCP, and front-end generation tasks.
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
Sizing the family
“I was just chilling on Ollama, as you do, and I noticed this new Ornith Oh, Ornith Ornith updated 5 days ago, a self-improving family of open-source models for agentic coding. And it intrigued me. I began to...”
The model ships as a 9B dense, 31B dense, 35B mixture-of-experts, and a 397B MoE; the 397B is claimed comparable to Opus and built on pretrained Gemma and Qwen 3.5, but at a 4-bit quant it is still 223GB, too big for a 128GB M-series Mac, so the practical picks are 9B for chat and 35B for coding. Write down each model variant with its parameter count and your machine's RAM, then mark which ones you could realistically load at 4-bit quantization.
5:03
Run it on Mac
“context. The client's data said the production build, which resulted in specific non-condescending consequences. I mean, it's pretty I'm looking at this now. So, it's pretty, you know, to the point and and whatever. It's gets the job...”
He runs the 9B on MLX/OllamaX (not plain Ollama, which lacks MLX support and runs poorly on Mac), gets ~22 tokens/sec, and notes OllamaX caches to SSD so a follow-up 'soften the tone' prompt is far faster; the 9B writes a passable but blunt firing email, about what you'd expect from that size. Install MLX or OllamaX, download a 9B model, and time a first prompt versus a cached follow-up to feel the SSD-caching speedup yourself.
10:46
Agentic front-end test
“straightforward coding, I think. Okay, so let's put it through some generic front-end tests here. This is a blank project, so it's literally got free reign. So I'm going to say design me uh landing page with the...”
Using OpenCode with the 35B MoE and Webflow plus Chrome MCPs, the model generated a decent-but-generic landing page from live site content in ~10 minutes but failed to push a page to Webflow via MCP and, being non-vision, couldn't verify its own screenshots; verdict is a reasonable local option for simple hobby projects, not frontier work. Point a local coding model at a real front-end task through OpenCode with an MCP connected and note exactly where it succeeds versus where MCP or lack of vision makes it fail.
01
Brief
Start with this video's job: A hands-on walkthrough of downloading and running a new self-improving open-source coding model family (9B, 31B, 35B MoE, and 397B MoE variants) locally on a Mac using MLX and OllamaX, then stress-testing it against Qwen 3.5 with real email-writing, code-base, Webflow MCP, and front-end generation tasks. Treat "Brief" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “I was just chilling on Ollama, as you do, and I noticed this new Ornith Oh, Ornith Ornith updated 5 days ago, a self-improving family of open-source models for agentic coding. And it intrigued me. I began to...”
02
Source
Use "Source" to locate the part of the creative automation workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 5:03, where the video says: “context. The client's data said the production build, which resulted in specific non-condescending consequences. I mean, it's pretty I'm looking at this now. So, it's pretty, you know, to the point and and whatever. It's gets the job...”
03
Generation
Turn "Generation" into the reusable artifact for this lesson: A creative workflow board with critique criteria and review checkpoints. This is where watching becomes something you can inspect and reuse.
04
Selection
Use "Selection" 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
Edit
Use "Edit" 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
Taste Review
Use "Taste Review" 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 creative workflow board with critique criteria and review checkpoints..
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: A hands-on walkthrough of downloading and running a new self-improving open-source coding model family (9B, 31B, 35B MoE, and 397B MoE variants) locally on a Mac using MLX and OllamaX, then stress-testing it against Qwen 3.5 with real email-writing, code-base, Webflow MCP, and front-end generation tasks.
02
Explain the practical stakes without hype: New playlist item from Samuel Gregory; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Brief -> Source -> Generation -> Selection -> Edit -> Taste Review sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A creative workflow board with critique criteria and 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: Can This New Local AI Model Beat Qwen?
- URL: https://www.youtube.com/watch?v=OnKuAkok07I
- Topic: Creative Automation
- My current learning frame: Download a 9B and a mid-size MoE model via MLX/OllamaX, wire the larger one into OpenCode with an MCP, and run the same email-writing and landing-page prompts to judge for yourself whether the local model is good enough for your hobby coding.
- Why this matters: New playlist item from Samuel Gregory; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:00 / Evidence 1: "I was just chilling on Ollama, as you do, and I noticed this new Ornith Oh, Ornith Ornith updated 5 days ago, a self-improving family of open-source models for agentic coding. And it intrigued me. I began to..."
- 1:44 / Evidence 2: "tasks uh with a bit more knowledge. 35 billion probably for a lot more coding and 397 for some real coding. Let's get it downloaded. Let's get things set up the way I like to set up uh..."
- 5:03 / Evidence 3: "context. The client's data said the production build, which resulted in specific non-condescending consequences. I mean, it's pretty I'm looking at this now. So, it's pretty, you know, to the point and and whatever. It's gets the job..."
- 8:24 / Evidence 4: "know there'll be people down in the comments telling me my prompt is crap and all the rest of it. First of all, I'm going to tell you that this is a perfectly acceptable prompt. And in fact,..."
- 10:46 / Evidence 5: "straightforward coding, I think. Okay, so let's put it through some generic front-end tests here. This is a blank project, so it's literally got free reign. So I'm going to say design me uh landing page with the..."
- 13:44 / Evidence 6: "code bases, but if there's something you want to see, let me know and I can make these reviews a lot better. So, I think this is a pretty fair comparison to make with Quen 3.5. It's definitely..."
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 creative workflow board with critique criteria and review checkpoints.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Brief -> Source -> Generation -> Selection -> Edit -> Taste Review
- 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 "Can This New Local AI Model Beat Qwen?", not a generic Creative Automation 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.
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 creative workflow board with critique criteria and review checkpoints..
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 model runner does the presenter prefer on the Mac, and why does he avoid plain Ollama for this model?
Which variant of the new model family is claimed comparable to Opus, and why can't he run it locally?
What limitation caused the model to fail verifying its own front-end work with the Chrome MCP?
Source shelf
Use the video as a doorway, then verify with primary sources.
