Skip to content

v20 monthly report shows per day rows by default #1109

Description

@shekharnwagh

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

  1. Use [email protected] or [email protected]
  2. Run:
npx [email protected] monthly
  1. Observe that the monthly table includes extra per-model rows for each day. For comparison, [email protected] monthly only 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

  1. github-actions commented on May 20, 2026

    @github-actions
    Contributor

    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 replies lgtm, your future issues and PRs will stay open.

    See CONTRIBUTING.md.

  2. changed the title [-]Since v20.0.0 monthly report also lists data for each day[/-] [+]v20 monthly report shows per day rows by default[/+] on May 20, 2026
  3. ryoppippi commented on May 24, 2026

    @ryoppippi
    Member

    thanks

  4. added a commit that references this issue on May 25, 2026
    bf84d4b
  5. ryoppippi commented on Aug 31, 2026

    @ryoppippi
    Member

    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 main implementation covers this request. This item is kept for history and does not need to be reopened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriage:resolvedResolved by a later change or current implementation.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions