CommandCodeAI / CommandCodeAI/command-code

Show usage per API key

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

Nobody has claimed this yet.

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

Description

Summary

Allow users to see the usage of individual API keys in addition to the overall usage. This allows users to see which apps, services, agents are using or bleeding tokens.

Expected Behavior

When clicking the Usage tab on the Command Code website, there should be an option to cycle through a list of currently issued API keys, and display the usage for those keys only. OpenCode Go has a good implementation of this feature.

Actual Behavior

Only overall usage is displayed. This means someone who issued multiple API keys can not see which keys are using the most tokens. I can see I used 6 Kimi K2.7 calls yes, but from which of my agents??

Steps to reproduce the issue

Sign into Command Code
Click on Usage

Command Code Version

1.26.0

Operating System

Other

Terminal/IDE

ghostty

Shell

bash

Session file (optional)

No response

Fix prompt (optional)

No response

Additional context

This is a feature on the website, user dashboard. Not in the harness.

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

Start at the Command Code website's Usage tab and trace how overall usage is loaded and rendered; use the referenced OpenCode Go implementation as a comparison. Done means users can cycle through their issued API keys and view usage for the selected key, while overall usage remains available.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.