Repository navigation
Free tier issues: read this first, then post your report here #59387
Description
This is the main issue for free tier problems. If you see any of these, you're in the right place:
Free usage exceeded, subscribe to GoFree usage limit reachedYou've used today's free messages. They reset at ...and the reset never happensThis version of OpenCode Desktop no longer supports free modelsOpenCode's free tier can only be used from within OpenCodeOpenCode 1.18.0 or newer is required to use the free tier
Please comment here instead of opening a new issue. We're closing duplicates and pointing them here so everything is in one place.
1. Make sure you're on the latest OpenCode v2
Most free tier reports come from OpenCode v1 (versions 0.x and 1.x, for example Desktop or CLI 1.19.5). v1 no longer supports free models and only gets fixes for critical bugs. Updating to v2 has fixed this for many people.
Check your version:
- Terminal:
opencode --version - Desktop: Settings → About
The latest v2 release is 2.2.1.
Important
The v1 Desktop app's built-in updater keeps you on 1.x. Download v2 manually from https://opencode.ai/v2/docs.
Desktop
Download v2 Desktop for macOS, Windows or Linux from https://opencode.ai/v2/docs, or on macOS:
brew install --cask opencode-desktopTerminal (TUI / CLI)
All install options are listed at https://opencode.ai/v2/docs. The quickest on macOS and Linux:
curl -fsSL https://opencode.ai/v2/install | bashOr use a package manager:
npm install -g @opencode/cli
bun install -g --trust @opencode/cli
brew install anomalyco/tap/opencode-v2
paru -S opencode-betav1 and v2 both use the opencode command. If you installed v1 with a package manager, remove it first, for example npm uninstall -g opencode-ai. Windows package managers (Chocolatey, Scoop) don't support v2. On Windows, use the Desktop app, npm, or a standalone binary.
Useful docs
2. Other things to check
- Free models only work inside OpenCode. Other clients, proxies and direct API calls can't use them. Use a paid model or Go there instead.
- Subscribed to Go but still seeing free limits? Run
/connect, sign in with OpenCode Console in your browser (make sure you authorize the workspace with your Go subscription, or choose OpenCode Go if you use a Go API key), then pick a Go model (opencode-go/...) with/modelsrather than a free model (opencode/...-free). - Hit the real daily limit? Wait for the reset time shown, subscribe to Go, or connect another provider with
/connect.
3. Still broken on the latest v2? Comment with:
- OpenCode version, and whether you use Desktop, TUI, CLI or web
- Operating system
- The free model you used
- The exact error message (a screenshot is fine)
- When it started and the reset time you were shown
- Whether you have Go or Console credits
Warning
Don't post email addresses, payment details or other account information here. This issue is public.
4. Still don't know what's going on?
If you're on the latest v2 and none of the above helps, or the problem is about your account, billing or Go subscription, email [email protected] with the details from step 3. Billing and account issues can't be fixed in GitHub issues.
Activity
opencode-agent commentedon Oct 26, 2026
Thanks for setting up this thread. Every problem listed here is decided by the hosted free tier service: usage limits, reset times, version checks and blocks on clients other than OpenCode. Reproducing any of them takes a real OpenCode account calling the free models, and this automated sandbox has no access to one. So none of them were reproduced here. Each report posted in this thread will need a maintainer with account access to look at it.
leostacowskicompasso commentedon Oct 26, 2026
Here is my report:
OpenCode v2.1.4 TUI on Windows 11 Pro 25H2
Error message started on the first time I used OpenCode today (10-26-26).
Tried with my two Zen accounts, same errors on all models I've tried so far.
Did not use OpenCode in two full days, was working fine on friday.
I don't have any credits. Only Zen free-tier.
Already tried without success:
public.My current setup since migrating from v1 is pretty bare-bones, no custom plugins no custom codebase.
All of my tracked requests on Zen's Logs have
inference_failederrors with 429:Love this tool, would greatly appreciate any feedback/workaround for this.
neriousy commentedon Oct 26, 2026
@leostacowskicompasso update to v2 please!
leostacowskicompasso commentedon Oct 26, 2026
Mentioned on my report!
Screenshot:
kenjaku-dev commentedon Oct 26, 2026
opencode v2.1.4
arch lunix
tomatomario45-sys commentedon Oct 26, 2026
Opencode TUI v2.1.4 on Windows 11 Pro 26H2
Deepseek V4.1 Flash Free
This error started yesterday at 7-8pm.
I've tried everything, but nothing worked.
I don't have any credits, just a free zen account.
micy99 commentedon Oct 27, 2026
Opencode 2.1.4 confimed.
monbooo090 commentedon Oct 27, 2026
I was previously advised to use v2, as the issue where the OpenCode Console free
tier was exhausted after just a single request had reportedly been fixed there.
Following this instruction, I switched to v2. While it worked as expected for
the first day, the issue unfortunately recurred the very next day. After sending
just one request, I was blocked again with the following message:
You've used today's free messages. They reset at 2026/10/28 9:00.
It appears the underlying problem has not been completely resolved in v2. Could
you please investigate the root cause and provide a permanent fix?
Thank you for your help.
opencode/latest/2.1.4/desktop
Kapie77 commentedon Oct 27, 2026
I hit the 24-hour limit and waited for 24 hours to pass, then I sent ONE message and got the 24-hour limit message again. This happened to me TWICE.
It seems that if, after 24 hours, I send a message in an old session, I hit the limit again instantly; I have to create a new session to avoid this bug, but then I lose all my work.
I’ve already tried switching models (I use the free ones) and it didn’t work; I’ve already switched computers, restarted the modem, tried resetting the sent message and sending it again, and created new sessions, but nothing works.
I use the standard free version of OpenCode (2.1.4, desktop version for Windows) and some free models.
NthanLim commentedon Oct 27, 2026
i have a same problem as @Kapie77, how to resolve this problem?
JackChen890311 commentedon Oct 27, 2026
Opencode Version: 2.1.4
OS: MacOS 27.0.1
Model: DeepSeek v4.1 Flash Free / MiMo v2.6 Flash Free / Big-Pickle
This starts today and I haven't sent any message yet.
Yesterday was fine.
vaibhavpandeyprayag commentedon Oct 27, 2026
Same thing happened with me, after 24 hours, sending single request hits the limit again (message of reset after 24 hr)
bilibili-CLY commentedon Oct 27, 2026
Same problem as @leostacowskicompasso :
Opencode v2.1.4 TUI on macOs 26.2. Every Zen Free Model returns the same message. First time found out on 10-25-26 at 10pm. No credits on my account. Have tried the methods above.
534 remaining items
mhollerb commentedon Nov 12, 2026
Follow-up to #59387 (comment): the issue also reproduces with stock OpenCode, without our integrations.
On November 12, 16:34–16:36 UTC, we tested the official OpenCode 2.2.5
run --standalonewith a fresh HOME, configuration, database and cache. Production state and/etc/opencodewere hidden in a temporary process namespace. No gateway, OpenEpoch, custom tools, workspace instructions, credentials or paid fallback were involved.Using identical report prompts and synthetic evidence (approximately 25 KB, 15 lines), with matching evidence-read outputs verified by hash:
The failures indicated approximately 7 hours 25 minutes until reset, but the separate-turn test succeeded immediately afterward. This also shows that the single-message prefix is not a reliable workaround.
This is a small sample, not proof of the underlying cause or a guaranteed workaround. It does establish that the failure is not confined to our custom integration. The tests used synthetic data and made no production changes.
valledemena commentedon Nov 13, 2026
I've been watching this thread for weeks and the pattern is clear:
My proposal (issue #63368) offers a concrete alternative:
This design especially helps open-source developers who don't pay now but may become subscribers when their projects grow; it gives them a stable, predictable experience without invisible walls.
If you want OpenCode to be your go-to AI agent — not just an experiment you abandon when the free tier blocks you — vote with 👍 on #63368. The bot has already indexed it with explicit maintainer review; with community pull we can turn proposal into policy.
He estado siguiendo este hilo durante varias semanas y el patrón es claro:
Mi propuesta (issue #63368) ofrece una solución concreta:
Esta arquitectura beneficia especialmente a los desarrolladores de código abierto que no pagan ahora pero podrían convertirse en suscriptores cuando su proyecto crezca; les brinda una experiencia estable y predecible sin penalizarlos con muros invisibles.
Si quieres que OpenCode sea la herramienta de IA que uses de forma continua -- y no solo un experimento que abandonas cuando el free tier te bloquea -- vota con 👍 en #63368. El bot ya lo ha indexado y lo ha etiquetado para revisión de los mantenedores; con el apoyo de la comunidad podemos pasar de "propuesta" a "política".
neekimyong commentedon Nov 13, 2026
I was only able to use it for 1 hour. If this is how it’s going to be, shouldn’t the notice about the 24-hour restriction be removed?
VariableVince commentedon Nov 13, 2026
Could this issue be one of the reasons for the free tier problems? Interrupted sessions silently continue in the background. Unnoticed until you see output somewhere like a github comment. If you have many old sessions with free models, do they just immediately eat all the allowed free usage somehow? Please beware: i have NOT seen this myself, not in the Console at least there was no usage that i didn't know the source of. But it may be part of the problem.
Still waiting for a fix. My paid subscription has ended in the meantime since this and other fundamental issues (not able to use free models at all, plan mode allowing edits so agent creates and writes to files without your knowledge, MCPs and opencode-cli.exe with the Python.exe from those mcps not closing on close, restarting Interrupted sessions silently in background, etc), continue to go unsolved. It's an unusable product and all that is fixed is less important than these fundamental problems. Maintainers ignore or underestimate impact or are (even more scary) incompetent. Also how do they expect me to trust a deeply flawed product like this when it comes to things like security and safety of my data?
Please have the better devs (the fullstack ones, the backend ones, not talking about those who only do UI or so) fix fundamental problems before getting them to continue work on less important things.
suuniqo commentedon Nov 14, 2026
I have the same issue in macOS using v2:
You've used today's free messages. They reset at 1:50 AM.
Upgrade to OpenCode Go → /connect · Switch model → /models
By turning off my WiFi, sending a message and getting an error, reconnecting and sending another message, I managed to fix it. However I am unable to trigger the error again, so I can't see if that works consistently.