The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗Know what a message will cost before you send it.
A free browser extension for claude.ai that predicts how much of your 5-hour and weekly Claude limit a message will use, tells you which model and effort level are enough (with reasons), and learns your plan over time. Everything runs in your browser.
⬇ Add to Chrome — free, from the Chrome Web Store
Chrome Web Store · Website · Releases · Türkçe README
▶ Watch the full walkthrough on YouTube (4 min) · Türkçe
47-second intro video and a live demo of the real prediction engine are on the website. The interface in the video is illustrative; the numbers come from the extension's own engine.
Claude Code shows your usage. The claude.ai chat screen does not. On claude.ai you open Settings → Usage, and there you only see what you have already spent. Limits often run out in the middle of a job, on a message you did not expect to be expensive.
Token Forecast brings that into the chat and goes one step further: it tells you before you press send.
| Feature | Settings → Usage | Usage meters* | Token Forecast |
|---|---|---|---|
| 5-hour and weekly percentage, reset time | ✅ | ✅ | ✅ |
| Inside the chat, next to the message box | ❌ | ✅ | ✅ |
| What this message will cost, before sending | ❌ | ❌ | ✅ |
| Which model is enough, and why | ❌ | ❌ | ✅ |
| Hidden cost of switching model mid-chat | ❌ | ❌ | ✅ |
| Roughly how many tasks the remaining limit allows | ❌ | partly | ✅ |
| Learns from your plan and habits | ❌ | ❌ | ✅ |
| "Why was that message so expensive?" explanation | ❌ | ❌ | ✅ |
| Weekly report, hourly heatmap, personal tips | ❌ | partly | ✅ |
| Cache and peak-hour countdowns | ❌ | partly | ✅ |
* We looked at the pages of eight usage extensions in October 2026. None offered a per-message estimate before sending or a reasoned model suggestion; all show usage after sending. One has a cache countdown, one a peak-hour countdown, one a heatmap.
A small pill shows the percentage of your limit the message will use, with an 80% range. Open Why? to see the detected task, the topic, what the extension looked at, and the basis for the suggestion (Anthropic's model-choice guide). If it is not sure, it never suggests a light model.
From Low to Max: which effort level is enough for this task, and how much limit you would save if your current setting is higher. It knows each model's default and the Extra high level.
"I need a website with a translation system" is a build job, not a translation. The extension tells the difference and does not suggest Haiku. The automated tests contain 15 trap sentences like this plus real translation requests.
Your 5-hour and weekly limits, what the remaining limit still allows (short questions, explanations, code fixes…), the weekly report, and the state of your personal calibration.
Messages, limit spent, peak-hour share, model and task mix, topic and effort mix, a 7×24 hourly heatmap, the most expensive messages, forecast accuracy, a learning-proof chart and personal tips. Computed only in your browser from text-free records. Monday-morning notification, CSV export.
This is the beginning of the README. Read the rest at the original. Read the full README ↗