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
Model list offers variants for opencode/big-pickle that the runtime refuses (Variant unavailable) #56012
The server's model list offers low, medium (default), high and xhigh for opencode/big-pickle, and every one of them is refused at run time:
$ opencode run -m "opencode/big-pickle#medium" "Reply with the single word: ok"
Error: Variant unavailable for opencode/big-pickle: medium
$ opencode run -m "opencode/big-pickle#high" "Reply with the single word: ok"
Error: Variant unavailable for opencode/big-pickle: high
$ opencode run -m opencode/big-pickle "Reply with the single word: ok"
ok
Other models in the same list take their listed variants: opencode/cat-jam-free#medium and opencode/deepseek-v4.1-flash-free#high both answer.
A client that builds its reasoning picker from the model list (T3 Code does) offers choices for Big Pickle that always fail, and a session started on the listed default medium fails with provider.no-route.
Environment
@opencode/cli 2.0.30, Linux x64
Related: #42848, the same error for a model whose catalog entry lists no variants.
Thanks for the detailed report. I tried this on @opencode/cli 2.0.30 (Linux x64) and got the same runtime error: opencode run -m "opencode/big-pickle#medium" (and #high) fails with Variant unavailable for opencode/big-pickle: medium (or : high), while plain opencode/big-pickle and opencode/cat-jam-free#medium answer normally.
I couldn't reproduce the mismatch with the model list, though. On 2.0.30 the server's model list (GET /api/model, e.g. opencode api model.list) returns "variants": [] for opencode/big-pickle, with no default variant. That is the same answer you'd get from a private server (--standalone) or the background service. It also matches the models.dev catalog entry, which marks Big Pickle as reasoning: true with reasoning_options: []. cat-jam-free, by comparison, lists low/medium/high/xhigh/max. So the server lists no variants for Big Pickle and accepts none at run time, which is consistent.
The low/medium/high/xhigh choices with medium as default may come from the client building its own effort list for models marked as reasoning, rather than from OpenCode's list. That's similar to #42848. A few things would help:
the raw opencode api model.list output (just the big-pickle entry) from your machine, if it shows variants there
which endpoint or field T3 Code reads the variants and the default medium from
whether you use any config or plugin that adds variants to the opencode provider
Closing this for now, as we haven't heard back. On @opencode/cli 2.0.30 I got the same Variant unavailable error for opencode/big-pickle#medium. But the server's model list (GET /api/model) shows "variants": [] for Big Pickle, which matches the models.dev catalog. So OpenCode lists no variants for this model and accepts none at run time. The low/medium/high/xhigh choices most likely come from the client (similar to #42848).
If your opencode api model.list output does show variants for big-pickle, please reply with that entry and how T3 Code reads the variants, and we can reopen this. Thanks for the report!
Activity
opencode-agent commentedon Oct 16, 2026
Thanks for the detailed report. I tried this on
@opencode/cli2.0.30 (Linux x64) and got the same runtime error:opencode run -m "opencode/big-pickle#medium"(and#high) fails withVariant unavailable for opencode/big-pickle: medium(or: high), while plainopencode/big-pickleandopencode/cat-jam-free#mediumanswer normally.I couldn't reproduce the mismatch with the model list, though. On 2.0.30 the server's model list (
GET /api/model, e.g.opencode api model.list) returns"variants": []foropencode/big-pickle, with no default variant. That is the same answer you'd get from a private server (--standalone) or the background service. It also matches the models.dev catalog entry, which marks Big Pickle asreasoning: truewithreasoning_options: [].cat-jam-free, by comparison, lists low/medium/high/xhigh/max. So the server lists no variants for Big Pickle and accepts none at run time, which is consistent.The low/medium/high/xhigh choices with
mediumas default may come from the client building its own effort list for models marked as reasoning, rather than from OpenCode's list. That's similar to #42848. A few things would help:opencode api model.listoutput (just thebig-pickleentry) from your machine, if it shows variants theremediumfromopencodeproviderRelated issues, ordered by likelihood:
Variant unavailableerror when a client defaults tomediumfor a reasoning model with no variantsreasoning_options: []show no thinking variantsopencode-agent commentedon Oct 19, 2026
Closing this for now, as we haven't heard back. On
@opencode/cli2.0.30 I got the sameVariant unavailableerror foropencode/big-pickle#medium. But the server's model list (GET /api/model) shows"variants": []for Big Pickle, which matches the models.dev catalog. So OpenCode lists no variants for this model and accepts none at run time. The low/medium/high/xhigh choices most likely come from the client (similar to #42848).If your
opencode api model.listoutput does show variants forbig-pickle, please reply with that entry and how T3 Code reads the variants, and we can reopen this. Thanks for the report!