Repository navigation
v20 monthly report shows per day rows by default #1109
Description
What happened?
Since v20.0.0, ccusage monthly shows extra per-model/day rows under each monthly aggregate by default.
Before v20, the monthly report showed only month-level rows with an agent subtotal. In v20.0.0 and v20.0.1, the all-agent monthly table expands model-level for each day automatically, which makes the report much noisier and feels closer to a daily view.
This appears to affect the table output only. The JSON output still returns one monthly object per period, with model details nested under modelBreakdowns.
Steps to reproduce
- Use
[email protected]or[email protected] - Run:
npx [email protected] monthly- Observe that the monthly table includes extra per-model rows for each day. For comparison,
[email protected] monthlyonly showed the month aggregate plus the agent subtotal.
Expected behavior
ccusage monthly should show month-level aggregate rows by default.
Per-model for each day, rows should either require an explicit breakdown option, or there should be a way to disable them.
Actual behavior
ccusage monthly expands per-model for each day rows by default in v20.
Version
Reproduced with:
Last known version without the expanded model rows:
Activity
github-actions commentedon May 20, 2026
This issue was auto-closed. Issues from new contributors are auto-closed by default.
Maintainers review auto-closed issues and reopen worthwhile ones. Issues that do not meet the quality bar in CONTRIBUTING.md may not be reopened or receive a reply.
Keep the issue short, concrete, and written in your own voice.
If a maintainer replies
lgtmi, your future issues will stay open. If a maintainer replieslgtm, your future issues and PRs will stay open.See CONTRIBUTING.md.
[-]Since v20.0.0 monthly report also lists data for each day[/-][+]v20 monthly report shows per day rows by default[/+]ryoppippi commentedon May 24, 2026
thanks
fix(all): collapse per-day rows in monthly/weekly all-agent table (cc…
ryoppippi commentedon Aug 31, 2026
Historical audit: this discussion was auto-closed by the legacy contributor gate. That closure did not assess technical importance.
Audit result: resolved. A later merged change or the current
mainimplementation covers this request. This item is kept for history and does not need to be reopened.