ZCode Runs GLM 5.2 for Free — Z.ai's New Coding Agent With 5M Daily Tokens
This video reviews Zcode, Z.ai's new Codex-style coding agent tuned for GLM 5.2, covering the model's benchmark position (strongest open-weights coder, MIT licensed, 1M context), the app's workflow features like goal mode and click-to-edit previews, its rough edges, and the aggressive free tier of 5 million daily tokens.
AI Stack Engineer9 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 AI Stack Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to evaluate a model-lab-owned coding agent — reading benchmark gaps honestly (medium versus marathon-length tasks), weighing data-routing and licensing tradeoffs, and judging whether the pricing and workflow fit your daily coding rotation.
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,629 cleaned transcript words reviewed across 474 timed caption segments.
Thesis
ZCode Runs GLM 5.2 for Free — Z.ai's New Coding Agent With 5M Daily Tokens teaches a practical coding-agent workflow move: This video reviews Zcode, Z.ai's new Codex-style coding agent tuned for GLM 5.2, covering the model's benchmark position (strongest open-weights coder, MIT licensed, 1M context), the app's workflow features like goal mode and click-to-edit previews, its rough edges, and the aggressive free tier of 5 million daily tokens.
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:18
GLM 5.2 in context
“it like OpenAI's Codex or Anthropic's Claude code, except it's built by ZAI specifically for their own GLM models. And because it's tuned by the same people who trained the model, it tends to squeeze more out of...”
GLM 5.2 is a 744B-parameter MoE (about 40B active) with a real 1M-token context and MIT license, scoring 51 on the Artificial Analysis index versus Opus 4.8's 56 — near-parity on Frontier SWE (74.4 vs 75.1) but trailing Opus by 13 points on SWE Marathon's longest tasks, with no image understanding and Z.ai cloud data falling under China's National Intelligence Law unless you self-host. Write a two-column tradeoff sheet for GLM 5.2 versus your current closed model: benchmark deltas, license rights, data-routing concerns, and which of your real tasks are 'medium' versus 'marathon' length.
4:33
Tour the rough edges
“prompt, the agent starts working. Up top, you'll see the thread title, and on the right, there's an option to open the project in any editor you want, plus a toggle panel button that opens up a full...”
Zcode mirrors Codex's agent-first layout with a one-click skills marketplace, MCP servers, sub-agents, quota tracking, and a live preview where you can click any element to reference it in chat — but it lacks a file explorer, a full change-log view, worktrees, and in-app Git initialization, because it is young and shipping fast. Install Zcode's trial, run one small feature build, and keep a list of which missing power-user features (file browsing, Git, change log) actually block your workflow versus merely annoy.
6:17
Goal mode and pricing
“markdown files, and each one can be pinned to a different model. So, you could set a cheap model for a read-only research agent and save your GLM 5.2 quota for the agent that actually writes code. Right...”
Goal mode hands the agent an objective and it plans, edits, runs checks, and self-reviews until the goal verifiably passes, with remote steering from WeChat, Feishu, or Telegram via QR pairing; the free tier gives 5M daily tokens (3M GLM 5.2 + 2M GLM 5 Turbo) for 5 days, and paid plans at $16/$64/$144 a month undercut Claude Code and Cursor, with GLM coding plan users getting roughly 1.5x quota through July 31. Define one verifiable goal for a small repo (with a concrete pass condition), run it in goal mode without intervening, and compare the token spend against what the same task costs in your current tool.
01
Inspect context
Start with this video's job: This video reviews Zcode, Z.ai's new Codex-style coding agent tuned for GLM 5.2, covering the model's benchmark position (strongest open-weights coder, MIT licensed, 1M context), the app's workflow features like goal mode and click-to-edit previews, its rough edges, and the aggressive free tier of 5 million daily tokens. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:18, where the video says: “it like OpenAI's Codex or Anthropic's Claude code, except it's built by ZAI specifically for their own GLM models. And because it's tuned by the same people who trained the model, it tends to squeeze more out of...”
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 4:33, where the video says: “prompt, the agent starts working. Up top, you'll see the thread title, and on the right, there's an option to open the project in any editor you want, plus a toggle panel button that opens up a full...”
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 reviews Zcode, Z.ai's new Codex-style coding agent tuned for GLM 5.2, covering the model's benchmark position (strongest open-weights coder, MIT licensed, 1M context), the app's workflow features like goal mode and click-to-edit previews, its rough edges, and the aggressive free tier of 5 million daily tokens.
02
Explain the practical stakes without hype: New playlist item from AI Stack Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
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: ZCode Runs GLM 5.2 for Free — Z.ai's New Coding Agent With 5M Daily Tokens
- URL: https://www.youtube.com/watch?v=3RvzXHCc6CU
- Topic: Creative Automation
- My current learning frame: Use Zcode's 5-day free trial to run one real repo task end to end — a goal-mode build with a verifiable pass condition, then a click-to-edit refinement pass in the preview — and record cost, quality, and missing features to decide if it earns a spot in your rotation.
- Why this matters: New playlist item from AI Stack Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:18 / Evidence 1: "it like OpenAI's Codex or Anthropic's Claude code, except it's built by ZAI specifically for their own GLM models. And because it's tuned by the same people who trained the model, it tends to squeeze more out of..."
- 1:58 / Evidence 2: "is only four points behind the best closed model. On SweBench Pro, it hits 62.1, which actually beats GPT 5.5 at 58.6, though Opus still leads at 69.2. Where I think the story gets more honest is the..."
- 4:33 / Evidence 3: "prompt, the agent starts working. Up top, you'll see the thread title, and on the right, there's an option to open the project in any editor you want, plus a toggle panel button that opens up a full..."
- 6:17 / Evidence 4: "markdown files, and each one can be pinned to a different model. So, you could set a cheap model for a read-only research agent and save your GLM 5.2 quota for the agent that actually writes code. Right..."
- 8:44 / Evidence 5: "every model lab now wants to own the environment, not just the model. Anthropic has Claude Code, OpenAI has Codex, and now ZI has Zcode. They've all decided that owning the place where you spend your day is..."
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 "ZCode Runs GLM 5.2 for Free — Z.ai's New Coding Agent With 5M Daily Tokens", 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.
Where does GLM 5.2 stand against Opus 4.8 on the long-horizon coding benchmarks, and what does the video conclude from that?
What interactive editing feature does Zcode's preview panel offer, and what key tooling is still missing from the app?
What does Zcode's free trial include, and how does goal mode change how you work with the agent?
Source shelf
Use the video as a doorway, then verify with primary sources.
