Media
3 items
Description
Predicts when you'll hit your Claude 5-hour and 7-day limits, and alerts you before you get there. ■ LATEST UPDATES Version 1.6.0 * Reset alerts can now also be delivered to your phone through ntfy.sh, so you hear about a reset while you are away from your PC * The badge can switch to the time until the next reset once nothing is left, instead of sitting at 0% * More history is kept — up to 3,000 readings, roughly a month of collection Version 1.5.0 * Gaps in the chart can now optionally be filled with an interpolated line, so the trend stays readable across missing periods * More reliable reset notifications — each reset is now announced once, without repeats Version 1.4.1 * Forecast advice is colored by urgency, so a run toward 100% stands out * Clearer handling of the "limit already reached" state, including when it was reached * Tooltips on the chart show the time behind each point * If the selected window has no forecast, the other one is shown Version 1.4.0 * Added the usage forecast chart, for both the 5-hour and 7-day windows * Organizations are shown one at a time, and your last selection is remembered ■ KNOW BEFORE YOU HIT THE LIMIT claude.ai shows how much of your usage window you have used, and when it resets. It does not estimate when your current pace will reach the limit. Claude Usage Monitor answers the question you have before you start working: will I hit the limit before the next reset? It tracks your 5-hour and 7-day usage windows in the background, estimates your pace from recent and overall trends, and projects that pace forward to the reset. So instead of only seeing "62%", you get an estimate like "2h 15m until 100%" — and, right next to it, the chart that estimate came from. If that puts the limit before your reset, you know it now, rather than two hours from now with a half-finished task in front of you. Claude Usage Monitor is an unofficial, independent extension, not affiliated with or endorsed by Anthropic. Your usage history is stored locally in Chrome and is not transmitted to the developer or to any third party. ■ THE FORECAST The forecast chart sits in the popup, directly under your current usage. It draws three things together: * Where the window started — backfilled from the last reset at 0% * Your actual usage so far — every reading collected since then * The projected line to the next reset — where your current pace leads So you can inspect the trend behind the estimate rather than taking a number on faith. A slow, steady climb and a sudden burst both produce "62%", but they lead to very different places, and the chart shows which one you are in. Above the chart, one line summarizes what it means. It reads one of: * "2h 15m until 100%" — you are on track to run out before the reset * "Limit reached (3h 20m from start)" — you already have, timed from the first reading that showed 100% * "71.4% used at reset" — usage is expected to stay under the limit That line is colored by urgency, so a run toward 100% is visible before you read the words. Every marker has a tooltip with its recorded or estimated time: your current position, the last reset, the first reading collected, the projected end, the point where the limit is reached, and the next reset. Both windows are forecast independently, and a 5H / 7D toggle switches between them. If the window you selected has no forecast yet, the other is shown, so the panel is never simply blank. ■ HOW THE FORECAST IS CALCULATED Project from the last few minutes only, and one burst of activity throws the estimate off. Project from the whole window only, and you miss that your pace just changed. So the forecast blends both. Recent activity has more influence in the 5-hour window, which is driven by what you are doing right now. The longer-term trend has more influence in the 7-day window, which is driven by habits rather than by any single session. The 7-day estimate also adjusts for normal inactive hours. Projecting a full week as though you worked around the clock produces an unrealistic estimate, so the extrapolation is scaled toward a realistic waking-hours pace. That adjustment is reduced as the reset approaches, where it matters less. The forecast is an estimate, not a guarantee. It is most reliable when your usage is steady, and least reliable right after a window resets or when your pace changes sharply. When the required usage or reset data is unavailable, no forecast is displayed — you see "No forecast" rather than a guess. ■ THE BADGE AND RESET NOTIFICATIONS Most of the time, you should not have to open anything. The toolbar badge keeps a number in front of you all day. Choose what it shows: * Remaining usage — how much of the window is left * Time to reset — how long until the window rolls over * Off — if you would rather not have a number there Pick which window it tracks. The badge uses the same urgency thresholds as the popup, so its color and the bars inside the popup follow the same rules, which makes the status easy to scan at a glance. When you are signed out, or when usage cannot be read, the badge is hidden rather than left showing a stale number. Once the window is used up, "0%" stops telling you anything useful, so the badge can switch to the time until the next reset instead — the number you actually need at that point. It is optional, and it switches back on its own as soon as usage recovers. You can also get a desktop notification when a 5-hour or 7-day reset is detected — the point at which the work you were waiting on becomes possible again. Each window can be enabled independently, and small server-side timing differences are ignored, which reduces false reset notifications. Clicking a notification opens the visualization page. ■ PHONE NOTIFICATIONS A desktop notification only reaches you if you are at your desk. Reset alerts can also be delivered to your phone, through the free ntfy.sh app, so you find out that the window rolled over while you are away. Because your phone is outside the browser's reach, the alert is scheduled in advance for the time the window is due to reset. It arrives even if Chrome is closed or your PC is off. * Off by default. Turning it on asks for access to ntfy.sh, and nothing is sent until you grant it. * Alerts go to a private, randomly generated topic that only you register in the ntfy app. A setup guide is one click away in the settings panel. * Only the fact that a window has reset is sent — never your usage numbers, organization name, or account details. * It follows the same per-window switches as the desktop alerts, and it adds to them rather than replacing them. * Changes made offline are applied as soon as you are back online, so a setting never quietly fails to take effect. ■ HISTORY AND CHARTS Open the visualization page for the full history behind the forecast: * 5-hour and 7-day windows plotted together as step-area charts * Per-model limits overlaid as their own series and labeled by model name, so you can see which particular model you are using up * Extra credit usage on a separate chart, when it is enabled on your account * Ranges: 24 hours, this week, last week, this month, last month, or all time * Granularity from 1 minute up to monthly * Reset markers and a warning line, so you can see where past windows ended * A switch between remaining and utilization, and between local time and UTC * Zoom and pan, individual series you can show or hide, and a chart height you can drag to resize Gaps in collection are drawn as gaps rather than smoothed over with a straight line. If the browser was closed for six hours, the chart says so instead of inventing a trend across the missing period. You can optionally have those gaps bridged with an interpolated line when you would rather follow the overall trend. Up to 3,000 readings are kept locally — roughly a month of continuous collection — with the oldest dropping off as new ones arrive. ■ ORGANIZATIONS, SETTINGS, AND EXPORT If your account belongs to more than one organization, the popup shows them one at a time and remembers which one you were looking at. Organizations with no usage data are skipped rather than shown empty. Clicking an organization card opens the visualization page with that organization already selected. Settings live in one panel, reachable from the popup, the visualization page, or a right-click on the toolbar icon, and changes apply immediately everywhere: * Language — English or Japanese * Theme — light or dark * Badge — what it displays, which window it tracks, and whether it shows the time left at 0% * Notifications — 5-hour and 7-day resets, independently, on the desktop and optionally on your phone You can export your stored history as JSON at any time, and open an exported file to view it. Files opened this way are read-only and are never merged into your own stored data, so there is no risk of mixing someone else's readings into your history. ■ GETTING STARTED 1. Install the extension. 2. Sign in to claude.ai, if you are not already. 3. Open the popup. It fetches your current usage right away. You can get a forecast from the first successful reading. The last reset provides the starting point, so the extension does not need days of accumulated history before it can project anything — though the estimate does become more reliable as more readings accumulate within a window. After that, it runs on its own. Usage is collected in the background and appended to your local history, and there is a manual refresh button in the popup whenever you want a reading immediately. ■ PRIVACY AND PERMISSIONS Usage history is stored in Chrome local storage on your own machine. It is not transmitted to the developer, to advertisers, or to any third party, and it is never sold or used for advertising. No separate account or sign-up is required for the extension itself. JSON export runs only when you click export. The extension requests three Chrome permissions — storage, alarms, and notifications — plus host access limited to claude.ai. Storage holds your history, alarms schedule the background readings, and notifications deliver the reset alerts. Nothing else is requested up front. Access to ntfy.sh is optional and requested only if you turn on phone notifications. In that case the extension schedules the reset alert with ntfy.sh — the fact that a window resets and when, and nothing more. Your usage history, organization names, and account details are never sent there. Leave the feature off and no permission is requested and no request is ever made. It contains no content scripts, so it cannot read or modify the content of claude.ai pages — not as a matter of policy, but because it has no access to them. Apart from those optional phone alerts, the only network requests it makes are to claude.ai, using your existing session, to read your own usage data. ■ IMPORTANT LIMITATIONS You need to be signed in to claude.ai for usage data to be collected. While you are signed out, the extension hides the usage cards and says so, rather than showing old numbers as though they were current. It reads internal claude.ai endpoints that are not a published API and can change without notice. When they change, this extension can stop reporting until it is updated. Keeping up with those changes is an ongoing part of maintaining it. Utilization is reported as a percentage of your window, from 0 to 100. claude.ai does not expose the absolute number of credits or messages remaining, so that cannot be displayed. The interface is available in English and Japanese. This extension does not automate sending messages, bypass or work around usage limits, alter how claude.ai behaves, or access unrelated websites.