feat: add today and this-week shortcut commands #1300

Activity

1. pullfrog commented on Jun 12, 2026

   

   pullfrogBot

   on Jun 12, 2026 – with Pullfrog

   Contributor

   More actions

     ^{｜ Build this ➔ ｜ Make a plan ➔}
2. github-actions commented on Jun 12, 2026

   

   github-actionsBot

   on Jun 12, 2026 – with GitHub Actions

   Contributor

   More actions

   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.
3. github-actions

   closed this as completedon Jun 12, 2026
4. pullfrog

   added

   enhancementNew feature or requestNew feature or request

   on Jun 12, 2026
5. ryoppippi commented on Jun 14, 2026

   

   ryoppippi

   on Jun 14, 2026

   Member

   More actions

   we had weekly, but actually today command sound really good lol

   🎉React with 🎉1Reacted by Urda
6. ryoppippi

   reopened this on Jun 14, 2026
7. zengzuo613 commented on Jun 14, 2026

   

   zengzuo613

   on Jun 14, 2026

   Author

   More actions

   we had weekly, but actually today command sound really good lol

   Thanks for the recognition! Like "today", "this-week" is basically just a shortcut for something people do often — it'd be great to also add a "this-month" option.
8. jsiu93 commented on Jun 15, 2026

   

   jsiu93

   on Jun 15, 2026

   Last edited by jsiu93

   More actions

   I opened #1321 with an implementation for the today and this-week shortcuts.

   Adding a bit more context: I also need this for my own workflow. My company tracks weekly token usage, so having a direct ccusage this-week shortcut makes the reporting flow much simpler than calculating dates manually each time.

   Happy to defer if @lushi516 is already working on an implementation. I already had a tested local version and wanted to share it for review.
9. ryoppippi commented on Jun 15, 2026

   

   ryoppippi

   on Jun 15, 2026

   Member

   More actions

   for week, why not jq?
10. ryoppippi commented on Jun 15, 2026

    

    ryoppippi

    on Jun 15, 2026

    Member

    More actions

    we just want to keep ccusage as minimal as possible.
    today does make sense, for week, just use jq to get that last row from ccusage weekly?
11. jsiu93 commented on Jun 16, 2026

    

    jsiu93

    on Jun 16, 2026

    More actions

    That makes sense, thanks for clarifying.

    I agree this-week overlaps with the existing weekly command, and using jq for the latest weekly row keeps the command surface smaller.

    today still feels like a useful shortcut to me because it maps to a common single-day quick check, but I’m happy to narrow the PR to today only if that fits the project direction better.
12. zengzuo613 commented on Jun 17, 2026

    

    zengzuo613

    on Jun 17, 2026

    Last edited by zengzuo613

    Author

    More actions

    Excuse me. I have an alternative idea to the one I proposed earlier.
    I'd like to propose adding a -l, --last parameter to the daily, weekly, and monthly commands to output statistics for the most recent N units:
    

    ccusage daily --last 1     # today
    ccusage weekly --last 1    # this week
    ccusage monthly --last 1   # this month

    
    This keeps the existing style consistent while making it easy to view today / this week / this month. Since all three commands share the same time-filtering logic and only differ in granularity (day / week / month), the parameter maps naturally to each command's unit, so the implementation stays clean and unified.
    @ryoppippi @jsiu93

    👍React with 👍2Reacted by Chris Ella and ryoppippi
13. ccusage

    deleted a comment from cursor on Jul 27, 2026
14. ryoppippi

    closed this as completedin #1498on Jul 27, 2026
15. ryoppippi commented on Aug 31, 2026

    

    ryoppippi

    on Aug 31, 2026

    Member

    More actions

    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.
16. ryoppippi

    added

    triage:resolvedResolved by a later change or current implementation.Resolved by a later change or current implementation.

    on Aug 31, 2026