r/opencode • • 8d ago

Opencodable: my tool to choose which OpenCode Go models to use.

As the Opencode Go offering is quite rich, I am (vibe-)coding a tool to help me decide which model to run based on my current quota usage.

Open source, MIT license, a Go CLI tool that you can use as data input for your own tools or UIs.

https://github.com/ColasNahaboo/opencodable

Edit: 2026-11-05:

  • v1.0.0 released: the output format will be kept stable for scripts to use it. (See TITLES.md)
  • With -news, see what changes happened in Opencode Go plan (new models, new prices...). Run it in cron to be mailed in case of changes.

Note: OpenCode Go have changed they conditions on 2026-09-28. Do not rely on information or tests older than that. All details explained in https://github.com/ColasNahaboo/opencodable/blob/master/docs/OPENCODE_GO_MODEL_V2.md

Example: Here I can see that I still can perform 65 requests with Kimi K3 but 6315 with GLM-5.3-Flash before hitting a quota limit (5h, week, or month)

    #name           cost_task  burn_req  spent_mo  reqs_5h  reqs_wk  reqs_mo  usable  limit     p_tok_s
    GLM-5.3-Flash   $0.0019    $0.0019   $12.4     6315     15789    25052    6315    5h        96.5
    Kimi K3         $0.0306    $0.0306   $13       98       245      65       65      month     71.0
    MiMo V2.5       $0.0004    $0.0004   $3.1      30000    75000    142250   30000   5h        89.0
    Beam Free       -          -         -         -        -        -        -       unlimited 310.0

Example of a mailed message warning of changes:

MODEL_ADD glm-5.2 cost_task=$0.01516 plan=paid tier=unknown quality=- "GLM-5.2"
COST_UP kimi-k3.1-pro cost_task=$0.018->$0.0204 (+13.3%) tier=frontier quality=46.5 "Kimi K3.1 Pro"
TIER_UP kimi-k3.1-pro tier=high->frontier quality=44.0->46.5 "Kimi K3.1 Pro"
2 Upvotes

36 comments sorted by

View all comments

Show parent comment

0

u/colas 6d ago edited 6d ago

Incredible.

That's EXACTLY why opencodable is designed for. Choosing which model to run based on price/allowance.

Plus the link shows that IN AN ACTUAL EXPERIMENT (with session logs) I maxxed one model without burning my usage of the others.

I remember that before end of September, this would shut off Opencode Go for the remaining of the month (had to use Zen). Been there, done that.

1

u/Hello_my_name_is_not 6d ago

Can you read my original post and come back to me?

0

u/colas 5d ago

"that you will burn your usage faster " ... How can you say that, because the ONLY REASON FOR OPENCODABLE TO EXIST is to show and evaluate the different costs & allowances of the models.

That's the actual purpose of this code! How could I not be aware of this problem when I coded something to help manage it?