Skip to content

[FEATURE]:Show remaining quota ("N% left", $X left, resets-in) alongside used% on usage indicators #53939

Open

Description

@cep207

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before

Describe the enhancement you want to request

I'm an OpenCode Go subscriber. Usage indicators now show "N% used" (after the
fix in #52401), but I still keep misreading the quota state: I constantly think
the limit is almost exhausted right before heavy tasks, while in fact I still
have most of the plan left.

Request: show the remaining figure explicitly everywhere usage is shown:

  • both framings side by side: "64% used" and "~36% left"
  • absolute values where available: "$12.30 used / ~$27.70 left"
  • time until reset: "resets in 3d 12h"

Use case

When planning heavy work (pro models, long tasks), I need the answer to "how
much do I still have?", not "how much did I burn". Deriving it from a used%
creates constant anxiety about running out mid-task. Related history:
#52401 (inverted bars, fixed), #46274 (daily remaining, closed by bot).

Activity

  1. opencode-agent commented on Oct 8, 2026

    @opencode-agent
    Contributor

    Thanks for the detailed request, @cep207!

    To restate it: wherever Go plan usage is shown, display the remaining amount next to the used amount (e.g. "64% used · ~36% left"), dollar amounts where possible ("$12.30 used / ~$27.70 left"), and the time until reset. That way "how much do I still have?" can be read straight off the page.

    One note: the Go usage cards in the Console already show a "Resets in …" line under each bar. The other parts ("% left" and dollar amounts) aren't shown today. Showing dollar amounts would also need new data from the backend, because the usage data currently has only the percentage and the reset time.

    Maintainers will consider this. Related issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions