Repository navigation
Bug: quota --output json field current_interval_usage_count shows remaining quota, not usage #68
Description
Bug Description
When running `mmx quota show --output json`, the field `current_interval_usage_count` does not represent what its name implies.
Actual behavior: The value is the number of remaining calls available in the current interval.
Expected behavior: `current_interval_usage_count` should represent calls already used.
Steps to Reproduce
```bash
mmx quota show --output json --quiet
```
Sample output:
```json
{
"model_name": "MiniMax-M*",
"current_interval_total_count": 1500,
"current_interval_usage_count": 1417
}
```
If `usage_count = 1417` with `total_count = 1500`, the remaining should be `1500 - 1417 = 83`. However, the quota actually expires after ~83 more calls — suggesting `1417` represents the remaining quota, not used amount.
Suggested Fix
Rename `current_interval_usage_count` → `current_interval_remaining_count` to match the actual meaning, or add a separate field for actual usage.
Activity
xandersbell commentedon Apr 9, 2026
Fixed in PR #69 —
--output jsonnow addscurrent_interval_remaining_countandcurrent_weekly_remaining_countfields (semantically correct), while preserving originalusage_countfields for backward compatibility.--quietmode also corrected.xandersbell commentedon Apr 9, 2026
Updated: PR #69 now fixes the existing
current_interval_usage_count/current_weekly_usage_countfield values directly (no new fields, no schema change). Values are corrected to actual usage, resolving the semantic mismatch.xandersbell commentedon Apr 9, 2026
PR #69 update: initial commit added new fields (current_interval_remaining_count) for the correct semantics. After review, we reverted to fix only the existing field values in-place — no new fields, no schema change — to respect the original API contract.
RyanLee-Dev commentedon Apr 17, 2026
Fixd