Watercolor painting of a brass key before two arched doors, representing the Zen and Go services

Benchmarking OpenCode's Free Tier: 450-766 Requests/Day, Not the Rumored 200

If you build with, or are thinking of using, OpenCode.ai (oc, for short) for development or agent work, you’ve probably felt this anxiety: worried the models won’t match the official ones, worried the free tier will hit its limit every day, or puzzled over how the Go subscription quota is even calculated, especially with claims floating around about burning through half a month’s quota in 5 minutes. Once DeepSeek V4 Flash (ds4f, for short) stabilized, the token constraint issues became much easier to manage. I analyzed over 3,000 API call logs from my local machine across three months of active usage and cross-checked them against the numbers online. Here’s the truth behind these five misconceptions. Once you get these straight, your workflow runs steadier, and you stop worrying about burning through your token quota. ...

2026-08-10 · 4 min · Alex Wang
Watercolor: person sitting at computer with AI auto-organizing folders, scattered file icons nearby

Day 8: Autonomous AI, Automation Without Writing Code

This is Day 8 of Week 2 in the “AI Path L1→L2 Upgrade Guide.” You should have completed Day 7 first. On Day 7, you added error handling to your script. It now runs reliably in real network conditions. But there’s a more fundamental limitation: you still have to write code. Writing code to call APIs is one kind of automation. There’s a lighter one: describe the task, and let AI write the code, run it, and fix the bugs itself. That’s autonomous execution AI. ...

2026-06-28 · 6 min · Alex Wang

omo vs oms: Fallback Chains Deep Dive

This is Part 2 of When Your AI Coding Tool Needs Three Configs. Part 1 covered the config design, file structure, and orchestration philosophy. This article focuses on fallback mechanisms. omo = oh-my-openagent, oms = oh-my-opencode-slim. Model and provider names are anonymized as provider-a/model-x etc. Why Bother Understanding Fallback omo and oms both support fallback: automatic switching to backup when the primary model is unavailable. But their mechanisms differ completely: omo is a multi-layer pipeline that degrades step by step; oms uses startup model selection + runtime abort retry. You need to understand this difference to configure a reliable chain. ...

2026-06-07 · 13 min · Alex Wang

When Your AI Coding Tool Needs Three Configs

Why I Need Three OpenCode Configs I have three opencode.json files in my ~/.config/opencode/ directory. The reason is simple: I wanted to run oh-my-openagent (omo from here on) and oh-my-opencode-slim (oms from here on) side by side, comparing them to understand where each one’s boundaries lie. omo is the full version—it comes with a batch of built-in agents (Sisyphus, Atlas, Prometheus, Oracle, Explore, Librarian, Metis, Momus, etc.), plus the ones I register on demand. The core is the fallback chain and the Sisyphus orchestrator: throw a refactoring task at Sisyphus, and it breaks the task down for Prometheus to plan, Atlas to execute the plan and distribute subtasks, Explore to search code, Oracle to analyze, then Sisyphus aggregates the results. oms is the slim version—it also has an orchestrator as the main agent responsible for executing tasks, but the difference is in the review phase: oms uses council multi-model consensus, where multiple councillors review results in parallel, and the Council agent synthesizes outputs from all councillors to reach a final conclusion. ...

2026-06-05 · 10 min · Alex Wang
Watercolor: chat bubbles dissolving into a token stream flowing into a notebook and brass key on a desk

AI Path L1→L2 Upgrade Guide (1): Your First API Call

TL;DR: This is Part 1 of the “AI Path L1→L2 Upgrade Guide” series. Four parts total, one per week of practice. This article takes you from chat windows to APIs, automating your AI interactions through code, laying the foundation for batch processing and autonomous task-execution AI. Introduction: From “I Ask AI” to “Programs Ask AI” If you finished the L0→L1 graduation checklist, you might remember one line from the graduation post: “Register for an API account and use Python to print your first AI reply.” Today is that day. ...

2026-06-01 · 12 min · Alex Wang
Watercolor style: a neatly organized workbench with labeled glass jars, a leather journal, curated tools, and a two-drawer cabinet symbolizing tiered knowledge management

AI Path L0→L1 Upgrade Guide (4): Building Your Personal System

📖 This is Part 4 of 5 in the “AI Path L0→L1 Upgrade Guide” series. Part 1: Understanding Your Tools · Part 2: From Vague Questions to Precise Instructions · Part 3: Turning AI Into Your Collaboration Partner · Part 4: Building Your Personal System · Part 5: Graduation & Next Steps Over three weeks you’ve picked up follow-up questions, context management, role-playing… the skills are piling up, and here’s the problem: how do you manage all these scattered abilities in one place? Week 4 is about exactly that: building a prompt library, choosing the right tools, and setting up knowledge management. Turning what you’ve learned into a personal system. ...

2026-05-26 · 4 min · Alex Wang
Watercolor illustration: three artisan tools on a warm wooden workbench: a wide terracotta bowl, an elegant glass carafe, and a segmented wooden organizer, each suited for different tasks, no ranking implied

Pick Your AI by the Job, Not the Ranking

Tried ChatGPT, Claude, Gemini, DeepSeek… and still can’t decide which one to stick with? Here’s the thing: that’s the wrong question. There is no universally best AI, only the one that fits what you’re doing right now. What’s your scenario? “I want a general-purpose assistant for everything” → ChatGPT. As of May 2026 the default is GPT-5.5, well-rounded, with the richest plugin ecosystem. If you pick just one, this is a solid choice. ...

2026-05-15 · 1 min · Alex Wang
Watercolor illustration: three books progressing left to right: closed book with question mark, open book with magnifying glass, open notebook with mind map, symbolizing three cognitive shifts

Stop Using AI Like a Search Engine: 3 Cognitive Shifts

The last article covered a foundational idea: LLMs generate probabilistically. They don’t look up answers; they think them through fresh each time. That means response variance is normal, and you need to verify. Easy to understand. Harder to act on. The habit is sticky: open ChatGPT, type a phrase, grab the answer, close the tab. This post isn’t a tutorial. I picked three real scenarios to show what actually changes when you use AI differently. ...

2026-05-13 · 5 min · Alex Wang
Watercolor illustration: a person at a cozy desk, holding a glowing translucent orb representing the essence of understanding LLMs

AI Path L0→L1 Upgrade Guide (1): Understanding Your Tools

📖 This is Part 1 of 5 in the “AI Path L0→L1 Upgrade Guide” series. Series navigation will be updated once all parts are published. Introduction: Sound Familiar? I’ve watched a lot of friends use AI tools, and I keep noticing the same pattern. They’re not strangers to ChatGPT or Claude, using them casually from time to time, but their experience is wildly inconsistent. Sometimes the AI delivers a jaw-dropping answer; other times it completely misses the point, producing something unusable. ...

2026-05-11 · 5 min · Alex Wang
AI Toolchain Evolution Path panorama: five levels from First Contact to AI Native

The AI Path: From First Contact to AI Native

TL;DR: How does a person grow with AI? This post maps the journey from “opening a chat box for the first time” to “thinking in AI-native ways” across five stages—First Contact, Power User, Engineer, Architect, and Native. The essence of each stage isn’t about learning more tools, but about a shift in mindset: from passively accepting outputs, to actively designing inputs, to orchestrating multi-agent collaboration, and ultimately reshaping your own cognitive framework. The interactive path map at the end lets you explore each stage in full detail. ...

2026-05-10 · 5 min · Alex Wang