OmniRoute + OpenCode: 100% Free AI Coding Setup, Free AI Gateway
This video walks through OmniRoute, a free open-source AI gateway that runs locally and pools 236 providers (90+ with free tiers, roughly 1.6 billion deduped free tokens per month) behind one OpenAI-compatible endpoint, then wires it into OpenCode step by step so a coding agent runs at zero cost.
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 set up a local AI gateway with auto-fallback across free provider tiers and connect any coding agent to it via a single base URL, API key, and exact model ID.
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,447 cleaned transcript words reviewed across 438 timed caption segments.
Thesis
OmniRoute + OpenCode: 100% Free AI Coding Setup, Free AI Gateway teaches a practical coding-agent workflow move: This video walks through OmniRoute, a free open-source AI gateway that runs locally and pools 236 providers (90+ with free tiers, roughly 1.6 billion deduped free tokens per month) behind one OpenAI-compatible endpoint, then wires it into OpenCode step by step so a coding agent runs at zero cost.
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
One endpoint, 236 providers
“Every coding agent I test on this channel has the same catch. The tool itself is free, but the model behind it is not. You install Claude code or open code or cursor, and then you hit a...”
OmniRoute sits between your coding agent and the providers: your tool sends requests to one local address and the router picks the destination, auto-falling back in milliseconds through four tiers (paid subscription, API keys, cheaper providers, then free tiers) when a quota runs out. Over 90 of its 236 providers have free tiers, totaling about 1.6 billion pool-deduped free tokens per month. Write down the four fallback tiers in order and note which tier your own setup would hit first if you refuse to pay anything today.
2:10
Install and dashboard tour
“tools are weekend projects that break constantly. This one is being maintained like an actual product. And there's one feature here I didn't expect at all, token compression. OmniRout can compress your prompts before they reach the model,...”
Install is one command (npm install -g, then run it) and the dashboard lives at localhost:20128 with default password 'change me'; everything stays on your machine as SQLite with encrypted credentials and no telemetry. Beyond routing, it ships token compression (RTK plus Caveman engines claiming 15-95% savings, e.g. 69 tokens down to 19), a 95-tool MCP server, combos with 17 routing strategies, and a health page showing cooldowns and circuit breakers. Install OmniRoute, log into the dashboard, and visit the Providers, Combos, Endpoints, and Health pages so you can name what each one controls before wiring in a client.
5:44
Wire in a coding agent
“Codex CLI, Gemini CLI, Cursor, Cline, Kilocode, and basically any tool that accepts a custom OpenAI compatible endpoint. The repo lists 16+ supported tools with setup docs for each. The pattern never changes. Base URL, API key, model...”
Every client needs the same three things: base URL (localhost:20128/v1 from the Endpoints page), an API key generated in the dashboard, and the exact model ID copied from the connected provider's page since arbitrary model names fail. The video configures one model first (Big Pickle) to isolate breakage, verifies a round trip, then adds MiniMax and notes combos can chain free providers so an agent never notices a quota running out. Connect one free provider, configure exactly one model in your coding agent, and send a test 'hello' before adding a second model, mirroring the one-model-first debugging habit.
01
Inspect context
Start with this video's job: This video walks through OmniRoute, a free open-source AI gateway that runs locally and pools 236 providers (90+ with free tiers, roughly 1.6 billion deduped free tokens per month) behind one OpenAI-compatible endpoint, then wires it into OpenCode step by step so a coding agent runs at zero cost. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “Every coding agent I test on this channel has the same catch. The tool itself is free, but the model behind it is not. You install Claude code or open code or cursor, and then you hit a...”
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 2:10, where the video says: “tools are weekend projects that break constantly. This one is being maintained like an actual product. And there's one feature here I didn't expect at all, token compression. OmniRout can compress your prompts before they reach the model,...”
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 walks through OmniRoute, a free open-source AI gateway that runs locally and pools 236 providers (90+ with free tiers, roughly 1.6 billion deduped free tokens per month) behind one OpenAI-compatible endpoint, then wires it into OpenCode step by step so a coding agent runs at zero cost.
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: OmniRoute + OpenCode: 100% Free AI Coding Setup, Free AI Gateway
- URL: https://www.youtube.com/watch?v=fXke2rmwOps
- Topic: Codex + Claude Workflows
- My current learning frame: Install OmniRoute, connect one no-auth free provider, wire your preferred coding agent to the local endpoint with a single copied model ID, then build a two-provider combo and confirm requests still succeed when the first provider is unavailable.
- 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:00 / Evidence 1: "Every coding agent I test on this channel has the same catch. The tool itself is free, but the model behind it is not. You install Claude code or open code or cursor, and then you hit a..."
- 2:10 / Evidence 2: "tools are weekend projects that break constantly. This one is being maintained like an actual product. And there's one feature here I didn't expect at all, token compression. OmniRout can compress your prompts before they reach the model,..."
- 3:57 / Evidence 3: "sounds for a tool that sits between you and every AI request you make. So, providers is where you connect accounts, and this is the page we'll use most. Combos is where you build fallback chains, so you..."
- 5:44 / Evidence 4: "Codex CLI, Gemini CLI, Cursor, Cline, Kilocode, and basically any tool that accepts a custom OpenAI compatible endpoint. The repo lists 16+ supported tools with setup docs for each. The pattern never changes. Base URL, API key, model..."
- 7:35 / Evidence 5: "Back in the OmniRoot dashboard, same provider page, and I'm grabbing the MiniMax model ID this time. Copy it, back to open code provider settings, add another model, paste the ID, name it, submit. Now the model picker..."
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", not a generic Codex + Claude Workflows 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.
One agent should do every task.
Different tools have different strengths. Routing is part of the workflow.
More context is always better.
Relevant context helps; stale context causes drift and cost.
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 are the four tiers of OmniRoute's auto-fallback, in order?
What does OmniRoute's token compression feature do and what savings does it claim?
Why can't you type an arbitrary model name when adding OmniRoute as a custom provider in OpenCode?
Source shelf
Use the video as a doorway, then verify with primary sources.
