Stop Paying for Claude Code — Use This FREE Tool Instead
A step-by-step guide to running Claude-Code-level agent workflows for free by pairing ZCode, a free open-source agentic app, with NVIDIA's free API platform to access strong open models like GLM 5.2 and Kimi K2, including how to configure the provider, work around rate limits, and build real apps from prompts and screenshots.
AI Unlocked16 minTranscript found
Quick learning frame
Read this before watching.
AI-native interfaces are control surfaces for intent, artifacts, context, preview, inspection, and iteration.
New playlist item from AI Unlocked; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to assemble a free coding-agent stack by connecting an open-source agentic framework to a free model provider and to manage rate limits and privacy tradeoffs while using it.
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.
01Intent
02Canvas
03Artifact
04Preview
05Feedback
06Iteration
Deep lesson
Turn this video into working knowledge.
1,372 cleaned transcript words reviewed across 420 timed caption segments.
Thesis
Stop Paying for Claude Code — Use This FREE Tool Instead teaches a practical interfaces + open design move: A step-by-step guide to running Claude-Code-level agent workflows for free by pairing ZCode, a free open-source agentic app, with NVIDIA's free API platform to access strong open models like GLM 5.2 and Kimi K2, including how to configure the provider, work around rate limits, and build real apps from prompts and screenshots.
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
Free agent stack
“What if I told you that you don't need Codex, Claude Code, or Co-work to build your own AI agent, and you could still plug in some of the strongest open-source Chinese models on the planet for free?”
Building an agent needs two pieces, a model and an agentic framework that turns the model into an agent that reads files, calls tools, and acts; ZCode is a free open-source app that blends Claude Code, Co-work, and Codex, and NVIDIA's API platform provides free access to open models like GLM 5.2, Kimi K2, and Nemotron once you filter by free endpoints. Sign up for an NVIDIA API account, generate a key, and add it to ZCode as a provider, remembering to choose chat completions (OpenAI-compatible) and set the context window to 1 million tokens before testing the model.
8:01
Beat the rate limits
“click test model to confirm the connection. And there it is, connected. GLM 5.2 is officially live inside Zcode. >> Here's the number you need to know. Nvidia's free tier gives you 40 RPM, 40 requests per minute.”
NVIDIA's free tier gives 40 requests per minute, not 40 prompts, because one prompt can trigger many tool calls that each count as a request; multiple keys under one account share the same limit, so the workaround is creating several separate NVIDIA accounts and rotating providers when one hits its ceiling. Set up two or three separate NVIDIA accounts, add each as its own provider in ZCode, and practice switching between them the moment one starts throttling.
8:56
Prompt and image to code
“between models freely without constantly hitting the ceiling. That one trick alone makes a huge difference in how usable this setup is. Let's actually put this to work. And this time, we're not just organizing files, we're building...”
With GLM 5.2 selected and full file access, ZCode builds a working habit tracker from a single prompt by creating the HTML, styling it, and wiring the JavaScript step by step; because GLM 5.2 is multimodal, dropping in a login-screen screenshot lets it read the layout and generate closely matching HTML and CSS using the same free model. Point ZCode at an empty folder, prompt GLM 5.2 to build a small app, then feed it a screenshot of a simple interface and compare the generated result against the original image.
01
Intent
Start with this video's job: A step-by-step guide to running Claude-Code-level agent workflows for free by pairing ZCode, a free open-source agentic app, with NVIDIA's free API platform to access strong open models like GLM 5.2 and Kimi K2, including how to configure the provider, work around rate limits, and build real apps from prompts and screenshots. Treat "Intent" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “What if I told you that you don't need Codex, Claude Code, or Co-work to build your own AI agent, and you could still plug in some of the strongest open-source Chinese models on the planet for free?”
02
Canvas
Use "Canvas" to locate the part of the interfaces + open design workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 8:01, where the video says: “click test model to confirm the connection. And there it is, connected. GLM 5.2 is officially live inside Zcode. >> Here's the number you need to know. Nvidia's free tier gives you 40 RPM, 40 requests per minute.”
03
Artifact
Turn "Artifact" into the reusable artifact for this lesson: A UI critique sheet for judging whether an AI interface improves control. This is where watching becomes something you can inspect and reuse.
04
Preview
Use "Preview" 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
Feedback
Use "Feedback" 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
Iteration
Use "Iteration" 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 ui critique sheet for judging whether an ai interface improves control..
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 step-by-step guide to running Claude-Code-level agent workflows for free by pairing ZCode, a free open-source agentic app, with NVIDIA's free API platform to access strong open models like GLM 5.2 and Kimi K2, including how to configure the provider, work around rate limits, and build real apps from prompts and screenshots.
02
Explain the practical stakes without hype: New playlist item from AI Unlocked; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Intent -> Canvas -> Artifact -> Preview -> Feedback -> Iteration sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A UI critique sheet for judging whether an AI interface improves control.
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: Stop Paying for Claude Code — Use This FREE Tool Instead
- URL: https://www.youtube.com/watch?v=9A28wWlZa8Y
- Topic: Interfaces + Open Design
- My current learning frame: Wire ZCode to a free NVIDIA-hosted model, set up a couple of backup accounts to dodge the 40-RPM limit, and build one app from a text prompt plus one from a screenshot to test both the coding and multimodal workflows.
- Why this matters: New playlist item from AI Unlocked; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:00 / Evidence 1: "What if I told you that you don't need Codex, Claude Code, or Co-work to build your own AI agent, and you could still plug in some of the strongest open-source Chinese models on the planet for free?"
- 4:32 / Evidence 2: "sensitive or private data through a free API. Second, there are rate limits, and understanding those limits is key to using these models efficiently. So, stick with me. I'll break that down in a minute. Set a password,..."
- 8:01 / Evidence 3: "click test model to confirm the connection. And there it is, connected. GLM 5.2 is officially live inside Zcode. >> Here's the number you need to know. Nvidia's free tier gives you 40 RPM, 40 requests per minute."
- 8:56 / Evidence 4: "between models freely without constantly hitting the ceiling. That one trick alone makes a huge difference in how usable this setup is. Let's actually put this to work. And this time, we're not just organizing files, we're building..."
- 11:22 / Evidence 5: "Once it's done, I'll open the file directly in the browser. And there it is, a fully working habit tracker built from a single prompt, completely free with a model that costs nothing to run. >>..."
- 14:49 / Evidence 6: "available. DeepSeek Pro was extremely slow. I mean, genuinely slow. Nematron Ultra 3 performed well, and DeepSeek V4 Flash was solid and quick. And that's it. That's exactly how you run Claude code and Codex-level agent workflows completely..."
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 UI critique sheet for judging whether an AI interface improves control.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Intent -> Canvas -> Artifact -> Preview -> Feedback -> Iteration
- 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 "Stop Paying for Claude Code — Use This FREE Tool Instead", not a generic Interfaces + Open Design 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.
A beautiful page is automatically a good learning tool.
Learning requires sequence, active recall, feedback, and application.
Generated UI should be accepted as-is.
Generated UI needs critique, revision, and browser verification.
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 ui critique sheet for judging whether an ai interface improves control..
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 two pieces does the video say you need to build an AI agent, and what free tools supply them here?
Why can NVIDIA's 40 requests-per-minute limit disappear faster than expected, and what is the recommended workaround?
How does the video demonstrate GLM 5.2's multimodal ability beyond building from a text prompt?
Source shelf
Use the video as a doorway, then verify with primary sources.