See how much Claude and Codex quota you have left, and when it resets, without leaving your chat.
AI Usage Tracker puts a small dashboard on claude.ai and chatgpt.com. The browser extension adds a toolbar popup, local history, and alerts for approaching limits. Optional API analytics track provider-reported usage separately from your chat subscription.
Download for Chromium · Install userscript · User guide
Actual packaged interface with example data, not a live account reading. Rings show quota remaining; the summary banner shows percentage used.
- Keep resets in view. A draggable widget stays on the provider page. Use the popup for a quick check, or keep Chromium's side panel open.
- Get notified before a limit or reset. Choose the rules you want, test notifications, and snooze them when you need quiet.
- Spot changes over time. Local sparklines show recent usage. Stale readings keep their last-known values and an error state instead of looking like fresh zeroes.
- Keep personal and work snapshots in separate local profiles. Export history when you want a copy.
Dark and light themes are included. The interface supports English, Spanish, French, German, and Arabic, with RTL layout, reduced motion, and an optional high-contrast palette.
- Download AI-Usage-Tracker-chrome-v0.2.5.zip and extract it to a folder you'll keep.
- Open your browser's Extensions page. In Chrome, use
chrome://extensions; in Edge, useedge://extensions. - Turn on Developer mode, choose Load unpacked, and select the folder containing
manifest.json. - Sign in to Claude or ChatGPT normally. Visit the provider's usage page once, then open the tracker and refresh.
This is a self-hosted extension, not a Chrome Web Store listing. The ZIP is the normal install path. A signed CRX3 is also available for compatible managed/self-hosted setups; its signature does not remove browser distribution restrictions.
Install Tampermonkey or Violentmonkey, then open ai-usage-tracker.user.js and approve it in your manager.
The userscript provides the in-page widget and settings. It needs a Claude or ChatGPT tab to remain open for refreshes and alerts. It doesn't add a toolbar popup, side panel, or browser settings sync. Its build target is Chrome/Chromium 111+ or Firefox 115+; manager permissions also affect what works.
The Firefox extension builds locally, but this release does not include a Mozilla-signed XPI. A normal Firefox extension install is pending signing. Developers can load the local build temporarily without changing Firefox's signature checks. Mozilla distinguishes temporary testing from signed distribution.
Release files and SHA256SUMS.txt include checksums for the published assets. The guide covers updates, removal, and the optional local desktop bridge.
Settings in the packaged Chromium extension. Example profile; no account credentials.
In-page widget · Light theme · First run · Provider unavailable · Side panel
The widget capture uses an isolated local fixture page, not the live Claude website. All captures use example data. Icon review and preserved concepts.
Claude Web and Codex Web are quota windows from your signed-in provider session. API analytics are separate integrations, not extra chat quota. The guide lists each integration and its credential requirements.
Provider pages and session endpoints can change. Check the source and freshness labels, and use the provider's own usage page as the final reference. Forecasts, local price-table costs, context counts, and cache reuse are estimates. They aren't billing records or promises about future limits.
The tracker has no analytics service or remote relay. Usage history and snapshots are stored in your local browser or userscript-manager profile.
It isn't offline. It makes requests to the provider sites, and optional API integrations contact the corresponding provider. API credentials default to session or memory storage; persistent local storage is an explicit option, not a password vault.
Two optional settings send data elsewhere: browser sync copies selected preferences through your browser account, and webhooks send alert events to the endpoint you configure. Webhooks are off by default; provider details require a separate opt-in. File exports can also contain labels you entered. Review them before sharing.
See the permission and data guide before enabling integrations or the native bridge.
The local acceptance run used Node.js 24 with npm. Use Node.js 22.4 or newer for the full browser-verification workflow.
git clone https://github.com/SysAdminDoc/AI-Usage_Tracker.git
cd AI-Usage_Tracker
npm ci
npm test
npm run buildLoad dist/chrome as an unpacked extension. Builds also produce a local Firefox development package and the userscript. Run npm run test:runtime for fresh-profile, headless Chromium and Firefox checks; browser and driver setup is documented in the development guide.
The strict model checks pass. Other covered JavaScript still has a checked-in baseline of 1,147 TypeScript diagnostics; the test fails on increases, not on every existing diagnostic. Authenticated provider accounts aren't part of the local acceptance run.
If a provider stops updating, refresh its signed-in usage page and check Settings > Status. Open an issue with the version and a reviewed redacted support bundle. Don't attach cookies, tokens, or raw account responses.
Released under the MIT license. This is an independent project, not an official provider extension.