OmniRoute + OpenCode: 100% Free AI Coding Setup, Free AI Gateway - Claude Code Alternative Free
Pro Coder solves the usual catch with free coding agents (the tool is free but the model is not) by putting OmniRoute, a local open-source AI gateway, between OpenCode and 290-plus providers, 90-plus of which have no-credit-card free tiers. The video is a full walkthrough: install the gateway, add a free provider account, mint an API key, register it in OpenCode as a custom provider, and edit opencode.json to point at the gateway's base URL and model id.
Pro Coder8 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 Pro Coder; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to route any OpenAI-compatible coding agent through a self-hosted gateway so free-tier accounts, automatic failover, and prompt compression replace a paid API subscription.
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,396 cleaned transcript words reviewed across 430 timed caption segments.
Thesis
OmniRoute + OpenCode: 100% Free AI Coding Setup, Free AI Gateway - Claude Code Alternative Free teaches a practical coding-agent workflow move: Pro Coder solves the usual catch with free coding agents (the tool is free but the model is not) by putting OmniRoute, a local open-source AI gateway, between OpenCode and 290-plus providers, 90-plus of which have no-credit-card free tiers. The video is a full walkthrough: install the gateway, add a free provider account, mint an API key, register it in OpenCode as a custom provider, and edit opencode.json to point at the gateway's base URL and model id.
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:30
Gateway over paywall
“gateway. We will combine with this open code to test. So, watch the video till the end. Before everything, let me tell you what is OmniRout. OmniRout is a brilliant open-source gateway that connects your tool to 290...”
OmniRoute exposes one OpenAI-compatible endpoint in front of 290-plus providers, pooling roughly 1.53 billion free tokens a month and failing over to the next account the instant one hits its rate limit. Two internal compression engines, RTK and Caveman, strip noise out of oversized context like a giant git diff or test log, cutting 15% to 95% of tokens, and keys, prompts, and analytics stay encrypted on your own disk. Estimate your current monthly spend on a coding-agent API key, then list which of your prompts are mostly diff and log noise that a compression layer would shrink.
4:48
Wiring OpenCode in
“If you don't know how to install it, that's so easy. Just move to your browser and search for Open Code, and just copy this uh code here and paste it, and it will be downloaded, okay? Just...”
After installing the gateway globally and logging into the local dashboard at localhost:20128 with the default password "change me", you add a free-trial provider account and create a named API key. In OpenCode you then run the slash command for connect providers, pick "other" since OmniRoute is not on the built-in list, give the provider id and paste the key, and the credentials are saved. Install OmniRoute, change the default "change me" password immediately, add one free-tier provider, and create a dedicated API key named for the agent that will use it.
6:13
Model config and proof
“paste the ID just you have copied here. And you can write name whatever you want. I will just type deep seek version 4 flash, okay? Now, what you have to do is simply just select all and...”
You filter the gateway's model list to free only, copy the model id, and paste a config block into opencode.json that sets the gateway base URL plus that model id under a display name of your choosing. Relaunching OpenCode auto-selects it, or you pick it under the slash models menu, and a quick "hello" plus "which model are you" confirms the traffic is really going through the gateway. Edit your opencode.json with the gateway base URL and one free model, restart, then ask the agent which model it is and check the answer matches what you configured.
01
Inspect context
Start with this video's job: Pro Coder solves the usual catch with free coding agents (the tool is free but the model is not) by putting OmniRoute, a local open-source AI gateway, between OpenCode and 290-plus providers, 90-plus of which have no-credit-card free tiers. The video is a full walkthrough: install the gateway, add a free provider account, mint an API key, register it in OpenCode as a custom provider, and edit opencode.json to point at the gateway's base URL and model id. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:30, where the video says: “gateway. We will combine with this open code to test. So, watch the video till the end. Before everything, let me tell you what is OmniRout. OmniRout is a brilliant open-source gateway that connects your tool to 290...”
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:48, where the video says: “If you don't know how to install it, that's so easy. Just move to your browser and search for Open Code, and just copy this uh code here and paste it, and it will be downloaded, okay? Just...”
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: Pro Coder solves the usual catch with free coding agents (the tool is free but the model is not) by putting OmniRoute, a local open-source AI gateway, between OpenCode and 290-plus providers, 90-plus of which have no-credit-card free tiers. The video is a full walkthrough: install the gateway, add a free provider account, mint an API key, register it in OpenCode as a custom provider, and edit opencode.json to point at the gateway's base URL and model id.
02
Explain the practical stakes without hype: New playlist item from Pro Coder; 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: OmniRoute + OpenCode: 100% Free AI Coding Setup, Free AI Gateway - Claude Code Alternative Free
- URL: https://www.youtube.com/watch?v=WbUIFBN_8FM
- Topic: Creative Automation
- My current learning frame: Stand up OmniRoute locally, connect two different free-tier provider accounts, wire OpenCode to it through opencode.json, and run a real coding task long enough to watch the gateway fail over from the first account to the second.
- Why this matters: New playlist item from Pro Coder; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:30 / Evidence 1: "gateway. We will combine with this open code to test. So, watch the video till the end. Before everything, let me tell you what is OmniRout. OmniRout is a brilliant open-source gateway that connects your tool to 290..."
- 2:31 / Evidence 2: "our channel and hit the bell icon to also you never miss any update. So finally it installed and we have to just paste this one here and click enter. and it just moved to local host that..."
- 4:48 / Evidence 3: "If you don't know how to install it, that's so easy. Just move to your browser and search for Open Code, and just copy this uh code here and paste it, and it will be downloaded, okay? Just..."
- 6:13 / Evidence 4: "paste the ID just you have copied here. And you can write name whatever you want. I will just type deep seek version 4 flash, okay? Now, what you have to do is simply just select all and..."
- 8:12 / Evidence 5: "So, let's see in the next video, guys. And if you have anything, just let me know, okay? So, see you in the next video, guys. Happy coding."
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 "OmniRoute + OpenCode: 100% Free AI Coding Setup, Free AI Gateway - Claude Code Alternative Free", 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 do the RTK and Caveman engines do for your free quota?
Why must you choose "other" when connecting the gateway inside OpenCode?
What two values go into opencode.json to finish the setup?
Source shelf
Use the video as a doorway, then verify with primary sources.
