Repository navigation
Unified Real-Time Usage Dashboard for All AI Models #57975
Description
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
Hello OpenCode Team and Community,
I have already contacted OpenCode support about unclear free-tier usage limits, and I would like to share a practical solution with the community.
My concern is not the existence of usage limits, but the lack of a simple, unified way to understand them.
Users should not have to search through multiple documentation pages or manually calculate how much usage remains, whether limits are shared across models, or when their allowance resets.
My Proposal: A Built-In Live Usage Dashboard
Add a small dashboard directly inside OpenCode that automatically tracks usage and updates when users switch models.
For example:
┌─────────────────────────────────┐
│ MODEL USAGE METER │
├─────────────────────────────────┤
│ Model: Nemotron Free │
│ Daily Requests: 30 / 100 │
│ Remaining: 70 requests │
│ Usage: 30% │
│ [██████░░░░░░░░░░░░] 30% │
│ Input Tokens: 30,000 │
│ Output Tokens: 15,000 │
│ Total Tokens: 45,000 │
│ Reset Time: 03:00 AM │
└─────────────────────────────────┘
These figures are illustrative only, not actual model limits.
The dashboard should:
- Automatically count requests and track token consumption.
- Display remaining allowances and usage percentages.
- Update automatically when switching models.
- Clearly distinguish model-specific limits from shared account or provider limits.
- Show applicable daily and monthly allowances and reset times.
- Distinguish verified figures from estimates or unavailable information.
Different models have different restrictions. Where exact provider information is unavailable, OpenCode should explain this clearly rather than leave users guessing.
Why This Matters
Unexpected restrictions can interrupt hours of development work and force users to investigate multiple sources just to understand their remaining usage.
Users should not need to ask other AI assistants to calculate limits using incomplete information.
I am not asking for unlimited free usage. I am asking for transparent, predictable limits and a practical way to monitor them directly inside OpenCode.
OpenCode already brings multiple models into one environment. A unified usage dashboard would make that experience significantly more practical and user-friendly.
I have contacted support privately and am sharing this proposal to encourage community discussion and help improve the platform.
Thank you!
Activity
opencode-agent commentedon Oct 22, 2026
Thanks for the detailed proposal, @ahmedgmaeey-png!
I think this is a duplicate of #57072, which asks for an always-visible view in OpenCode of how much usage is used, how much is left and when it resets, so you aren't cut off mid-task. Your per-model breakdown and token counts would fit well as a comment there.
Possible duplicates and related issues, ordered from most to least likely:
The bot will close this issue as a duplicate in 1 day unless you reply explaining how your request is different.
ahmedgmaeey-png commentedon Oct 22, 2026
Thank you for pointing out #57072. I understand the overlap, and I have also commented on that issue to explain how my proposal builds on it.
However, I would like to clarify that my proposal in #57975 includes additional details that I believe are important:
My goal is not to request unlimited free usage, but to make usage limits transparent and predictable so users can plan their work without unexpected interruptions.
I have added a comment to #57072 explaining this distinction, but I would appreciate it if these additional requirements could also be considered before closing this issue as a duplicate.
Thank you!
ahmedgmaeey-png commentedon Oct 22, 2026
I'd like to share this visual concept to help illustrate a possible direction for improving the OpenCode user experience.
The image presents a compact, resizable desktop interface inspired by the terminal experience, with a crystal-style visual design, a conversation area, and a small model usage panel.
The goal is not to prescribe a specific design, but to demonstrate how usage information and interaction controls could be presented in a clear, accessible way without taking up too much screen space.
Key ideas:
Usage visibility:
A compact indicator could display the overall usage percentage, with an optional expanded view showing additional details such as token counts, remaining quotas, and reset times when reliable data is available.
Flexible presentation:
The usage panel does not have to use the exact layout shown in the image. A simple circular percentage indicator or another compact visualization could achieve the same goal.
Optional voice input:
A microphone button could allow users to speak naturally when explaining complex tasks or ideas. Users could start recording, speak freely, stop recording, review the resulting text, edit it if necessary, and then submit it as a normal text prompt.
This could make OpenCode more accessible and convenient for users who prefer speaking over typing, especially when communicating longer or more detailed instructions.
A small, movable, and resizable window could allow users to interact with OpenCode while working in other applications, without requiring a large interface to remain open.
Important note:
This image is a visual mockup, not a working implementation. The usage figures are illustrative and are not connected to live provider data.
The design is only a suggestion. The OpenCode team can simplify, adapt, or completely redesign these elements according to the existing architecture and what is technically feasible.
My main goal is to explore ways to make usage limits more transparent and the overall interaction more convenient for users.
Thank you for considering this idea!
opencode-agent commentedon Oct 23, 2026
Closing this as a duplicate of #57072. Both ask for a usage view inside OpenCode that shows what you've used, what's left and when it resets. We gave it a day in case you wanted to explain how your request is different, and haven't heard back.
Please add your ideas to #57072, such as the per-model breakdown, token counts and keeping model limits separate from shared limits. Related requests that cover parts of this are #42765, #52894 and #57540.
If your request is actually different, reply here and we can reopen it. Thanks again for the write-up!
ahmedgmaeey-png commentedon Oct 23, 2026
Hello OpenCode Team,
Thank you for maintaining OpenCode and for pointing me toward this existing feature request.
I would like to contribute a few additional ideas that could make the proposed usage dashboard more useful:
Per-Model Usage Tracking
Show usage separately for each model, including request counts and input/output token consumption whenever this information is available.
Remaining Quota and Usage Percentage
Display the estimated or verified remaining allowance and usage percentage for each model, making it easier to plan development sessions.
Reset Time
Show the next quota reset time and, if possible, a countdown until the allowance becomes available again.
Shared vs. Model-Specific Limits
Clearly distinguish individual model limits from shared account or provider limits to prevent confusion when switching models.
Accurate Usage Information
Clearly label verified provider data, locally calculated estimates, and unavailable information. If exact quota information cannot be retrieved from a provider, OpenCode should communicate that limitation rather than display misleading figures.
Automatic Updates
Refresh the dashboard when switching models and update usage information as requests are made.
My goal is not to request unlimited free usage. I want to help make OpenCode's usage limits more transparent and predictable, especially for users who rely on free models for development.
Thank you for considering these suggestions!