The episode opens with a cold the host picked up as his kids went back to school, and with the story behind the title: the previous episode was supposed to be called this, until DeepSeek-V 4-Flash-0731 landed and he found the OMP harness, and the rest was history. Now, he says, every road led back to GLM anyway. Since the last episode Z.ai shipped two things: GLM-5.3, the full model, and GLM-5.3-Flash, the smaller answer to a community that kept asking for a Flash or Air class model.

The Flash is only small in relative terms: 320 billion total parameters with about 18 billion active per token in a mixture-of-experts design, less than half the size of the full GLM models. It is natively multimodal with a vision encoder, carries a 1M-token context window, and uses a hybrid sparse plus linear attention design meant to hold long-context behavior while cutting compute overhead. The FP8 checkpoint is the primary release, full weights are on Hugging Face, including an Unsloth build, under an MIT license, and the model first surfaced publicly under the stealth codename Ox Alpha on OpenRouter and OpenCode.

Vision is the episode's real thesis, and the host's current local favorite is Native Precision GLM-5.3-Flash precisely because it can see. Web page, PDF and slide design obviously want vision, but so does his robotics work: pointing a webcam at the robot from the outside, or giving the model the robot's own camera, makes debugging behavior dramatically easier. He adds a less obvious use, compression techniques that employ vision models to squeeze context, and argues you only notice how much side-vision you rely on once you have it.

Then comes the joke that doubles as buying advice: asked which GLM 5.3 to use, the answer is basically all of them. The serious version is a prompting lesson in two scenarios. A satellite imagery company that wants people to search its photos for anything needs a general model with deliberately general prompting. A drone company flying over rooftop solar panels to find hotspots needs the opposite: a prompt loaded with what a hotspot is, what it looks like in thermal imagery, and task-specific detail.

Speed and failure behavior get an extended, honest segment. Fail-fast is the philosophy: a 16-minute failure beats a slow one, especially with a human in the loop who can redirect sooner. On his task DeepSeek V4 Flash fails in about 25 minutes, and its biggest problem is hallucination, confident wrongness that burns the clock. Token throughput gets numbers too: roughly 350 tokens per second on RTX 4000-class cards for the DeepSeek V2 Flash generation, with GLM-53-Flash not faster than DeepSeek V4 Flash, though a native run could close the gap. Full 100 percent GPU utilization, he notes, is rare: sometimes cards sit idle, sometimes they chew a trivial task.

The harness discussion centers on OMP, Oh My Pi, the open-source fork of Pi rebuilt as a coding-first terminal agent with native LSP integration, debugger support over DAP, model-agnostic role-based routing and token-efficient hash-anchored edits. OMP's character is to iterate longer, think and retry; the host's object-detection runs ask GLM 53 Flash through OMP to find objects in images, and his R and D loop runs through OMP as well. The open question he leaves hanging is whether to use OMP at all: different models may do better under a simpler framework, and harness choice is becoming a variable on par with model choice.

The robotics centerpiece is a split-brain demo: DeepSeek V4 Flash 0731 does the reasoning while a Qwen 27B model handles vision, with DeepSeek asking Qwen what it sees in the image and then issuing the joint commands that drive the arm forward or back. The combination works well, and he wonders whether the whole loop could run on Qwen 27B alone, noting a new Qwen model on the way. He would rather avoid APIs entirely but admits he might use DeepSeek or Qwen as the logic side. Watching the arm creep toward the block with fine wheel adjustments, he argues, reframes intelligence; watching the same model dither, overshoot, recalibrate and lose sight of the target reframes its absence.

Local inference gets the hardware-realist treatment. Native FP8 weights run about 306 to 328 GiB on disk with roughly 386 GiB of VRAM recommended for the default deployment, and BF16 roughly doubles that; compressed GGUF builds lower the floor to around 128 GB for a usable 3-bit setup and near 100 GB at 1-bit via llama.cpp or Unsloth. KV cache precision is a second knob with the same trade: cheaper cache, cheaper serving, softer reasoning. His Native Precision preference is a vote for keeping quality while paying the hardware bill instead of the token bill.

Money and hardware grief close the loop. The free Ox Alpha window shut on August 26, 2026, the day Z.ai revealed it as GLM-5.3-Flash; the paid route lists 0.15 dollars input and 0.50 dollars output per million tokens with a 50 percent promo (0.075 and 0.25) running through September 9, 2026, while OpenCode Go itself is 5 dollars for the first month and 10 dollars after. The host jokes the operation literally loses money and could print it with one small change. Then the RMA saga: an RTX Pro 6000-class card that stops under load, a seller who says RMA through Nvidia, Nvidia voices saying they know the firmware-level failure mode but have no known fix, and the suspicion he may be the first person in the entire US to RMA that card. Similar black-screen and fall-off-the-bus reports under inference load exist in Nvidia's own forums.

The closing message ties it together: GLM-5.3-Flash earns the homecoming because it bundles the three things his workflow actually needs, long-horizon agentic behavior, usable vision, and weights he can run himself. Benchmark chatter, including a fifth-place style ranking claim, is treated as vendor-adjacent noise until independent suites confirm it. The verdict is practical rather than tribal: run the harness you trust, measure fail-fast behavior on your own tasks, and let the model that survives contact with your robot win.

To steelman the other side: for pure-text coding with no camera, no PDF and no robot in the loop, DeepSeek V4 Flash 0731 is a serious alternative. Independent measurement puts its 0731 build at 50 on the Artificial Analysis Intelligence Index with Terminal-Bench 2.1 at 79 percent, and the hallucination rate, the exact weakness sentdex complains about, measurably improved. If your workload never touches vision, the faster pure-text model can be the rational pick.

What the video does not test is everything around the demo: a single host, a single camera, anecdotal timings, no controlled benchmark and no accounting of electricity or hardware cost. The security dimension of handing an agent terminal access plus webcam or on-robot camera feeds never comes up, yet that is precisely the setup the robotics demo normalizes. I treat every proper noun and figure from the auto-captions as unverified until a targeted search confirms it, and I confirmed the load-bearing ones, specs, prices and OMP identity, before writing.

Verifiability matters because two numbers in this story expire fast. The 50 percent launch promo on the API route, 0.075 and 0.25 dollars per million tokens, ends September 9, 2026 at 16:00 UTC, reverting to 0.15 and 0.50 dollars list; anyone deciding later must re-check the OpenRouter and Z.ai pages live. The FP8 weight and VRAM figures come from Z.ai's own serving recipe cross-checked against independent hardware analysis, while the RTX RMA saga is an N=1 anecdote: Nvidia forums do show similar Pro 6000 black-screen and Xid 79/154 reports under inference load, but that corroborates a pattern, not this card's diagnosis.

My practical takeaway is split by user type. For learning, tinkering, and keeping data on-device, especially robotics work where a camera feed must stay local, OpenCode or OMP plus a local GLM-5.3-Flash build is a genuine option I would try first. For shipping production secrets through free endpoints, hitting deadlines, or running teams on metered APIs, I would not: quotas, single-host flakiness and shifting monthly prices make that a hobby setup, not infrastructure. I will re-check every price at decision time.

AI commentary

"My read after watching: the headline is GLM, but the real story is vision plus local inference finally becoming practical. I would not pick a model on vendor charts; I would pick it on fail-fast behavior inside my own harness."

AI assessment

To steelman the other side: for pure-text coding with no camera, no PDF and no robot in the loop, DeepSeek V4 Flash 0731 is a serious alternative. Independent measurement puts its 0731 build at 50 on the Artificial Analysis Intelligence Index with Terminal-Bench 2.1 at 79 percent, and the hallucination rate, the exact weakness sentdex complains about, measurably improved. If your workload never touches vision, the faster pure-text model can be the rational pick.

What the video does not test is everything around the demo: a single host, a single camera, anecdotal timings, no controlled benchmark and no accounting of electricity or hardware cost. The security dimension of handing an agent terminal access plus webcam or on-robot camera feeds never comes up, yet that is precisely the setup the robotics demo normalizes. I treat every proper noun and figure from the auto-captions as unverified until a targeted search confirms it, and I confirmed the load-bearing ones, specs, prices and OMP identity, before writing.

Verifiability matters because two numbers in this story expire fast. The 50 percent launch promo on the API route, 0.075 and 0.25 dollars per million tokens, ends September 9, 2026 at 16:00 UTC, reverting to 0.15 and 0.50 dollars list; anyone deciding later must re-check the OpenRouter and Z.ai pages live. The FP8 weight and VRAM figures come from Z.ai's own serving recipe cross-checked against independent hardware analysis, while the RTX RMA saga is an N=1 anecdote: Nvidia forums do show similar Pro 6000 black-screen and Xid 79/154 reports under inference load, but that corroborates a pattern, not this card's diagnosis.

My practical takeaway is split by user type. For learning, tinkering, and keeping data on-device, especially robotics work where a camera feed must stay local, OpenCode or OMP plus a local GLM-5.3-Flash build is a genuine option I would try first. For shipping production secrets through free endpoints, hitting deadlines, or running teams on metered APIs, I would not: quotas, single-host flakiness and shifting monthly prices make that a hobby setup, not infrastructure. I will re-check every price at decision time.

Sources

glm-5.3-flash · vision · local inference