Usage limits
OpenCode Go usage limits explained
OpenCode Go publishes a monthly dollar limit for each model it serves. A 5-hour window allows 20% of that limit and a week allows 50%. JP measures your local Go usage against those published caps — a measured reading, not an official percentage.
Measured, not official: JP compares local Go spend with Go's published caps. OpenCode reports no remaining quota, so JP never shows an official percentage or a reset countdown.
Per-model dollar caps
Each Go model has its own monthly dollar limit on opencode.ai/docs/go, and dated promotions can raise one for a while. The 5-hour and weekly windows are fixed fractions of that monthly limit, so the model nearest its own cap is the one that binds.
How JP reads it
JP prices the Go-routed turns OpenCode logs in ~/.local/share/opencode/opencode.db at Go's published rates and shows 5-hour, weekly, and monthly usage against each model's cap, labelled measured. OpenCode stores no reset time or remaining quota on your Mac, so JP shows no countdown, and a model it cannot price adds nothing rather than a false 0%. Go dollars stay out of combined totals because the same turns also count under their model's row.
Common questions
- When do OpenCode Go limits reset?
- OpenCode records no reset boundary on your Mac, so JP measures trailing 5-hour, 7-day, and 30-day windows and shows no countdown.
- Does JP the Cat track OpenCode Go limits?
- Yes — OpenCode Go is live today. JP shows measured 5-hour, weekly, and monthly usage against Go's published per-model caps, labelled measured rather than official.