Claude-Code-Usage-Monitor · Issues· 37 open
Open on GitHubLocally synced open issues (discussions stay on GitHub)
- #31
brew support?
Updated Aug 5, 2026 - #235
Persist an audit trail for extra-usage transitions and provider-reported billing state
Updated Aug 5, 2026 - #238
The test suite does not run to completion on Windows
Updated Jul 31, 2026 - #158
[BUG] Incorrect Cost Usage calculation when continuing work in a resumed session
Updated Jul 31, 2026 - #234
Weekly usage / weekly reset day-time still not present in v4.0.0 (re: #167)
Updated Jul 27, 2026 - #233
Related-tools suggestion: claude-overnight (puts the idle quota your monitor shows to work)
Updated Jul 27, 2026 - #212
monitor dosnt look accurate
Updated Jul 25, 2026 - #231
On Windows, CCMonitor is tryingm to access WSL?
Updated Jul 22, 2026 - #229
Warehouse records are missing sessionId and isSidechain (subagent) from the source JSONL
Updated Jul 16, 2026 - #228
--api flag does not fetch/cache OAuth usage data despite valid credentials
Updated Jul 13, 2026 - #226
Session JSONLs are rewritten on resume/compact — historical usage numbers silently drift (repro + field data)
Updated Jul 11, 2026 - #223
Add --from/--to to daily and monthly view for more fine granular filtering
Updated Jun 30, 2026 - #187
API based claude code cost monitoring like LiteLLM
Updated Jun 21, 2026 - #214
You can monitor the /usage reliable just by running the PROMPT I have in the Gist. It uses the settings statusline
Updated May 20, 2026 - #209
support for tracking Claude.ai web (chat) and coworker usage in addition to Claude Code
Updated Apr 22, 2026