Who it is forA Claude subscriber who runs heavy sessions and wants to know how much of the 5-hour and weekly windows is left before work stops.
The problemWithout a visible meter, it is hard to tell how close you are to a usage window limit until you hit it.
The outcomeYou see the 5-hour and weekly usage windows as bars in the bottom right of Claude Code.
What you need first
- Claude Code installed and running
- Access to the /plugin command inside Claude Code
- A git repository with changes to commit, for the Commit plugin
- A system voice available on your computer, for the Narrator plugin
Steps
- Run
/plugin marketplace add midudev/better-claudein Claude Code. - Run
/plugin install sub-meter@better-claude. - Look at the bottom right of the Claude Code window.
- Check the bar for the 5-hour window and the bar for the weekly window.
- Plan heavy runs around the bars you see.
Prompt for your agent
In Claude Code on a subscription account with the better-claude sub-meter plugin installed, check the bottom right of the window for the 5-hour and weekly usage bars. Expected output: two bars showing current usage in each window. Verify that both bars are visible after restarting the session.
Caveat. The README does not say how often the bars refresh, so do not treat them as a live real-time count.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page