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
"Error from provider (Console): OpenCode's free tier can only be used from within OpenCode" in latest version of Open Code #49678
been getting this since about 2pm PST. not sure what's going on. thought maybe it was related to running an old version so I I updated latest version and it persists. I'd share what version but you've not bothered to report that anywhere standard, like "help > about", etc.
Plan mode, same model, same client/session: every request rejected with Error from provider (Console): OpenCode's free tier can only be used from within OpenCode
TL;DR: On 1.18.32, a custom agent with permission.bash: deny reliably fails Zen free models with "can only be used from within OpenCode"; the same agent with bash: ask succeeds (A/B/A/B). Built-in plan/build are fine. Not an external harness / missing-UA case. Workaround: use bash: ask (or omit bash) on agents that need free-tier models.
TL;DR: On 1.18.32, a custom agent with permission.bash: deny reliably fails Zen free models with "can only be used from within OpenCode"; the same agent with bash: ask succeeds (A/B/A/B). Built-in plan/build are fine. Not an external harness / missing-UA case. Workaround: use bash: ask (or omit bash) on agents that need free-tier models.
wow, that's exactly my config. deny bash. Only change from vanilla. what a silly rule/mistake to hinge all of this on! Note: have not confirmed yet this fixes the problem on my computer.
Some people say it depends on the version of OpenCode; others say it’s related to whether you’re using Plan or Build mode, or which tools are supported. But in my testing, none of those factors made a difference.
I suspect it has something to do with the network environment. OpenCode works fine on my home network, but I run into this issue on some public Wi-Fi networks.
Switching between v1 and v2, changing Plan or Build mode, using the original client, or installing plugins doesn’t seem to affect it. In my case, the issue appears to be network-related.
It's clearly some kind of decision model heuristic, no single factor but some weighted combo. But they've tuned to fire too easily! Uninstalling completely and reinstalling with the newest version did get it back to working for me. But now that Muse 1.3 is gone it's a lot less useful, anyway.
Closing this as a duplicate of #59387, the main issue for free tier problems.
Most of these reports come from OpenCode v1 (0.x / 1.x), which no longer supports free models. Updating to the latest v2 from https://opencode.ai/v2/docs fixes it for many people. The v1 Desktop updater keeps you on 1.x, so download v2 manually.
If you still have the problem on the latest v2, please comment on #59387 with the details listed there. For account, billing or Go subscription problems, email help@anoma.ly.
Activity
GOKUCODES-DEV commentedon Sep 18, 2026
same issue.
prititaliya commentedon Sep 18, 2026
same issue when i use the custom agents.
alanbork commentedon Sep 18, 2026
no custom agents. only non-default setting I have is disabling cmd/powershell
sekedus commentedon Sep 18, 2026
see my comment here.
alanbork commentedon Sep 18, 2026
Interesting you're suggesting that it's now required to have the TUI installed in addition to the GUI? That's bonkers if true.
ogerardin commentedon Sep 23, 2026
Same here, suddenly got this error in the TUI. Weirdly only in plan mode, build mode works normally.
Definitive evidence this is a server-side misclassification, not a client/auth problem.
Setup
opencode/big-pickleSymptom
opencode/big-pickle: worksError from provider (Console): OpenCode's free tier can only be used from within OpenCodeServer-side log of a rejected plan-mode request
{ "event": { "id": "4da00865-62b0-43d8-b7a2-a745761198b7", "requestID": "4da00865-62b0-43d8-b7a2-a745761198b7", "workspaceID": "wrk_01KJ1C8DEJBV25S2HS3F4CGMT1", "startedAt": 1790202247220, "finishedAt": 1790202247281, "durationMs": 61, "outcome": "rejected", "category": "inference", "protocol": "openai-chat", "product": "standard", "path": "/inference/openai/v1/chat/completions", "method": "POST", "stream": true, "app": "cli", "sessionID": "ses_f2fa18c58ffexKMjAQFym6hcI1", "userAgent": "opencode/1.18.32 ai-sdk/provider-utils/4.0.23 runtime/bun/1.3.14", "userID": "acc_01KJ1C8CR1GDYDE3P2E2VWSW6J", "requestedModel": "big-pickle", "provider": "opencode", "statusCode": 403, "errorCode": "Generation.FreeTierError", "errorMessage": "OpenCode's free tier can only be used from within OpenCode", "requestHeaders": { "accept": "*/*", "content-length": "383159", "content-type": "application/json", "user-agent": "opencode/1.18.32 ai-sdk/provider-utils/4.0.23 runtime/bun/1.3.14", "x-opencode-client": "cli", "x-opencode-session": "ses_f2fa18c58ffexKMjAQFym6hcI1" }, "responseHeaders": { "content-length": "120", "content-type": "application/json" }, "metadata": {}, "attemptCount": 0, "attempts": [] } }Why this proves server-side misclassification
Two details that may explain why only Plan mode fails
The known-working free-tier path documented in Free-tier Zen 403 for all third-party stacks despite valid session + key (only genuine client passes) #49621 is /zen/v1/responses.
If plan-mode requests route via a different protocol/path than build mode, the gate may
not recognize that route as "within OpenCode".
in the genuine-request set described in Free-tier Zen 403 for all third-party stacks despite valid session + key (only genuine client passes) #49621.
Trace IDs
Related: #49588 #49590 #49610 #49621 #33318
orangeguitar commentedon Sep 23, 2026
Cross-linking a controlled repro that may explain non-third-party reports of this error:
#49433 (comment)
TL;DR: On 1.18.32, a custom agent with
permission.bash: denyreliably fails Zen free models with "can only be used from within OpenCode"; the same agent withbash: asksucceeds (A/B/A/B). Built-in plan/build are fine. Not an external harness / missing-UA case. Workaround: usebash: ask(or omit bash) on agents that need free-tier models.ogerardin commentedon Sep 23, 2026
Setting bash to "ask" in plan mode fixed it.
Cheers!
alanbork commentedon Sep 23, 2026
wow, that's exactly my config. deny bash. Only change from vanilla. what a silly rule/mistake to hinge all of this on! Note: have not confirmed yet this fixes the problem on my computer.
copi143 commentedon Oct 18, 2026
Same issue; using the official client, no plugins installed.
vasilvestre commentedon Oct 20, 2026
Happens to me in opencode v2, dual installed with opencode v1
copi143 commentedon Oct 21, 2026
Some people say it depends on the version of OpenCode; others say it’s related to whether you’re using Plan or Build mode, or which tools are supported. But in my testing, none of those factors made a difference.
I suspect it has something to do with the network environment. OpenCode works fine on my home network, but I run into this issue on some public Wi-Fi networks.
Switching between v1 and v2, changing Plan or Build mode, using the original client, or installing plugins doesn’t seem to affect it. In my case, the issue appears to be network-related.
alanbork commentedon Oct 21, 2026
It's clearly some kind of decision model heuristic, no single factor but some weighted combo. But they've tuned to fire too easily! Uninstalling completely and reinstalling with the newest version did get it back to working for me. But now that Muse 1.3 is gone it's a lot less useful, anyway.
vasilvestre commentedon Oct 22, 2026
So.. headroom was the culprist. Worked with opencode1
neriousy commentedon Oct 27, 2026
Closing this as a duplicate of #59387, the main issue for free tier problems.
Most of these reports come from OpenCode v1 (
0.x/1.x), which no longer supports free models. Updating to the latest v2 from https://opencode.ai/v2/docs fixes it for many people. The v1 Desktop updater keeps you on1.x, so download v2 manually.If you still have the problem on the latest v2, please comment on #59387 with the details listed there. For account, billing or Go subscription problems, email help@anoma.ly.