claude-code-proxy
claude-code-proxy copied to clipboard
Feature Request - Monitor Usage limit
Hello, this tool is a to guide for understanding how ClaudeCode consumes our tokens and how it interacts with its API. It’s incredibly useful, but I’m running into a problem: I hit Claude’s usage limit much faster than I expect 😡, and I’m not sure why.
Maybe some ideas to improve Claude-code-proxy’s usage metering :
- Stopwatch-style token tracker
- Add a single-click “start/stop” control that measures an interaction and displays the exact token count in real time.
- That would make it clear how many tokens a single Claude Code action consumes — especially important because one user action often triggers many API calls.
- Time-range filtering and summaries
- Provide Date/Hour range selectors to filter displayed requests.
- Show a concise summary for the selected range: total input tokens, total output tokens, number of cached ones, and other key metrics.
- This makes it easy to spot spikes, identify heavy usages or flows, and correlate token use with specific sessions or features.
What do you think ? I can elaborate on this if you need.
Thanks.