CommandCodeAI / CommandCodeAI/command-code
Include filtering and API Key details in Usage section
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
This is a request based on the commandcode.ai user interface, specifically the Usage section.
When viewing the Usage section, the data is lacking a bit of context that could help users in managing their API utilization. Currently, it shows the Model, Mode, and Status, but this isn't helpful in determining the source of the activity when a specific model is used across multiple API key.
Fix:
Add an "API Key" column that shows which API key was associated with each activity in the table, and allow for filtering by key name, so a user can identify instances when a service associated with a particular key ramps usage unexpectedly.
Use Case
No response
Additional Context
No response
How important is this to you?
None
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Usage section and its activity table, then trace where the displayed Model, Mode, and Status data comes from. Add the associated API Key to each activity and support filtering by key name; done means users can identify activity by key and filter the table accordingly.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100