You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Free tier models (Big Pickle, Beam Free, Nemotron) fail with "free tier can only be used from within OpenCode" on official CLI and desktop app #56585
All free tier models fail instantly (~300-700 ms) with:
"OpenCode's free tier can only be used from within OpenCode.
Download it at https://opencode.ai and keep building."
Models tested (same error on all): Big Pickle, Beam Free, Nemotron 3.5 Lightning Free.
Clients tested: official TUI (opencode in terminal) and the desktop app. Both fail.
What I already tried:
opencode upgrade -> already up to date (2.0.32, installed via npm)
No VPN or proxy
Removed all stored credentials (opencode auth logout until opencode auth list showed "No authenticated integrations"), then logged in again with opencode auth login (OpenCode Console account) -> a single credential, same error
Fresh sessions
It seems to affect the whole free tier, not a single model. It worked before and stopped suddenly.
Plugins
None
OpenCode version
2.0.32
Steps to reproduce
Open OpenCode (TUI with opencode, or the desktop app).
Select any free model (Big Pickle, Beam Free, Nemotron 3.5 Lightning Free).
Send any message, e.g. "hola".
The request fails in under a second with: "OpenCode's free tier can only be used from within OpenCode. Download it at https://opencode.ai and keep building."
Thanks for the report and for listing everything you already tried. I think this is a duplicate of #56324, which describes the same failure: on official v2.0.32, starting today (2026-10-17), every free model fails at once with "OpenCode's free tier can only be used from within OpenCode", in both the TUI and the desktop app, even after logging out and back in. The rejection comes from the hosted Zen gateway, not from your local setup.
Possible duplicates and related issues, ordered from most to least likely:
We haven't heard back in the last day, so we're closing this as a duplicate of #56324. That issue covers the same problem: on official v2.0.32, every free model (Big Pickle, Nemotron and others) fails at once with "OpenCode's free tier can only be used from within OpenCode", in both the TUI and the desktop app, even after logging out and back in. Please follow #56324 for updates. Other reports found that switching networks (for example a phone hotspot or Cloudflare WARP) can work around it in the meantime. If your problem turns out to be different, reply here and explain how, and we can reopen this. Thanks for the detailed report!
Activity
opencode-agent commentedon Oct 17, 2026
Thanks for the report and for listing everything you already tried. I think this is a duplicate of #56324, which describes the same failure: on official v2.0.32, starting today (2026-10-17), every free model fails at once with "OpenCode's free tier can only be used from within OpenCode", in both the TUI and the desktop app, even after logging out and back in. The rejection comes from the hosted Zen gateway, not from your local setup.
Possible duplicates and related issues, ordered from most to least likely:
FreeTierErroron official 2.0.32 even with a Console login or API keyIf you want to check whether your network is involved, try another network, such as a phone hotspot. Please follow #56324 for updates.
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
opencode-agent commentedon Oct 18, 2026
We haven't heard back in the last day, so we're closing this as a duplicate of #56324. That issue covers the same problem: on official v2.0.32, every free model (Big Pickle, Nemotron and others) fails at once with "OpenCode's free tier can only be used from within OpenCode", in both the TUI and the desktop app, even after logging out and back in. Please follow #56324 for updates. Other reports found that switching networks (for example a phone hotspot or Cloudflare WARP) can work around it in the meantime. If your problem turns out to be different, reply here and explain how, and we can reopen this. Thanks for the detailed report!