CommandCodeAI / CommandCodeAI/command-code

Live model spending tracker (with consumed usage)

Open
#802 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
4k
Forks
350
PR merge metrics
No merged PRs in 30d

Description

Feature Description

Show percentage quota consumed in addition to net dollar pricing in the live model spending tracker.

Example

$1.1 spent (5.5% of your quota)
Or for a model with higher usage allotment (e.g. DS v4 Flash on CommandCode or Muse 1.3 on OpenCode):
$1.1 spent (1.8% of your quota)

Context

Pricing vs usage vs consumption is confusing even for the best of us. The pricing strategy is similar for both OpenCode and CommandCode. I believe reason for this might be model providers don't want the their model prices to be shown as lower than a given standard, Pure speculation from my end here though. So there are now two knobs to effectively control the same thing, (controlling how much inference your dollars get you), the model price and the usage allotment.

Solution

Just noticed this in opencode, would be pretty sweet to have in cmdc.

Image

I understand a pure pricing indicator though slightly helpful, doesn't fully resolve the confusion. For example, one might be puzzled why $1.1 spend consumes 6% of usage.

Show percentage quota consumed in addition to net dollar pricing.
$1.1 spent (5.5% of your quota)
Or for a model with more usage (for example DS v4 Flash on commandcode or Muse1.3 on Opencode)
$1.1 spent (1.8% of your quota)

Related Reddit thread: r/CommandCode - https://www.reddit.com/r/CommandCode/s/5T0zQXfXkE

How important is this to you?

Important for my workflow

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named in the issue. Start by locating the live model spending tracker and its existing dollar-pricing display, then trace where quota or consumed-usage data is available for each model. Done means showing percentage quota consumed alongside spending and reflecting different model allotments.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.