Why typed doesn't use 5-hour windows like Claude Pro

You've probably hit it on Claude Pro or Claude Max: you're in flow on a Sunday afternoon, the model goes quiet, and a banner tells you to wait 47 minutes for your usage window to reset. Then it resets, you finish the thing, and four hours later you hit a Tuesday-morning weekly cap you didn't know existed.

This is the rolling-window model. Claude Pro, Claude Max, and most major AI coding subscriptions use some flavor of it. typed doesn't.

What Claude's rolling windows are actually for

Rolling windows are a load-shaping tool, not a billing model. They let a vendor like Anthropic say "here's a quota" without committing to a real cap, so the bursty user who codes hard from 9pm to 1am hits a wall at 11:30 and goes to bed, spreading load away from peak hours.

That's a reasonable thing for a vendor to want. It just isn't a thing your work cares about. The window doesn't reset because you finished a task; it resets because the clock crossed a five-hour boundary. The two are unrelated, and the boundary is invisible until you slam into it.

What happens when you hit your typed quota

Monthly quota. One reset date. The dashboard shows remaining quota; the meter only goes down when you actually use tokens.

When you hit 100% of monthly quota, one of two things happens:

1. Default behavior: the next request returns a 429 with a one-click top-up prompt. You pick a denomination ($5, $10, $20, or $50), confirm, and you're back in. Top-ups expire 90 days after purchase, and they're consumed before next month's quota replenishes, so you don't lose unused balance on the reset.
2. Auto-top-up (opt-in): if you've enabled it in the dashboard, typed silently charges your chosen denomination, emails you a receipt, and the session continues uninterrupted. You can set a monthly ceiling so it can't run away.

There's no throttle. No "we'll degrade your tier for the next four hours." No 5-hour window. No weekly cap behind the monthly one. When your meter reads 73%, you have 27% left until reset, and that's the whole story.

What hitting the cap actually looks like

Concretely: your CLI makes its next API call, and instead of a streamed response it gets back a structured error. Status 429, body shape:

{
  "type": "error",
  "error": {
    "type": "quota_exceeded",
    "message": "monthly quota exceeded -- buy a top-up to continue, or enable auto-top-up in your dashboard",
    "remediation_url": "https://app.typed.cloud/dashboard/plan"
  }
}

Claude Code surfaces that message in the same red box it uses for any API error. You click through to the dashboard, hit one of the four top-up buttons, the checkout modal opens in-page (no redirect), and the purchase completes in a few seconds. Your top-up balance is active immediately - the next CLI request goes through.

If you turned on auto-top-up beforehand, none of that happens. typed sees the over-quota request, charges your card on file for your configured denomination, the request continues, and a receipt lands in your inbox. From the CLI's point of view, the call simply succeeded; you find out about the charge from the receipt or the next dashboard visit.

The math: a $5 top-up at typed's overage rates ($1.67/M input, $8.33/M output) buys roughly 1.5M tokens of a typical 80/20 input/output coding workload. That's a couple of hours of moderate Claude Code usage. A $20 top-up takes you most of a working day.

What this trades off

Honesty: monthly quota means typed has to size its quotas for actual coding workloads, not theoretical-peak ones. We did, and the per-token math favors typed on Sonnet and Opus tiers, where most production coding actually lives. On Haiku-equivalent traffic it's closer to a wash, and the launch post has the per-tier breakdown.

A vendor running rolling windows can advertise a nominally larger quota because they know most users won't approach it in any single window. We can't lean on that, so the headline number is bounded by what we'll commit to. The tradeoff: the number you see is the number you have. If 50M tokens covers your month, 50M is what you get - it doesn't quietly become 30M because you spent an aggressive Saturday.

When auto-top-up wins, when it doesn't

Auto-top-up is the right setting if you've ever been mid-deploy when a quota popped. Five dollars to keep a release moving is a no-brainer; a 429 in the middle of a kubectl rollout status watch is not.

It's the wrong setting if you treat your monthly quota as a budget rail. Some users explicitly want the 429 - it's the feedback loop that tells them "you're at the cap, decide what's worth $5 right now." Both modes are valid. We default off because a surprise charge is worse than a surprise pause.

What happens when the charge fails

Auto-top-up isn't bulletproof; cards expire, banks decline, fraud holds happen. When auto-top-up is on and a charge fails, typed returns a 402 instead of a 429, with a short cool-down before retrying so a hard-declined card doesn't get hammered every request. The error includes a link to /dashboard/plan to update your payment method. You can still buy a one-off top-up manually during the cool-down, since the cool-down is on auto-charge retries, not on your account.

This is the kind of edge case we'd rather call out than discover together at 11pm on a Friday. The default-off setting for auto-top-up exists for the same reason: we'd rather you opt into the convenience deliberately than wake up to a surprise charge on a misconfigured cap.

Does typed have a weekly cap?

No. The realistic shape of heavy usage is bursty, you'll spend three days in flow and then two weeks tuning configs. Rolling windows tax the flow days specifically. Monthly quota lets the flow days be flow days and quietly amortizes against the slow weeks.

If your usage genuinely runs hot every day, you should be on a tier where that's the assumption - typed Max is $100/month, the same as Claude Max 5x, and it sizes for sustained daily usage. Per-tier breakdown on the migration page; product landing at typed.cloud; sign in or create an account at app.typed.cloud.

FAQ

Does typed have a 5-hour window or weekly cap? No. Quota is monthly with one reset date. When you hit 100%, you get a 429 with a one-click top-up (or, if you've enabled auto-top-up, a silent recharge and a receipt).

What happens when I hit my typed quota? The next request returns a 429 with denominations to top up ($5 / $10 / $20 / $50). Top-ups expire 90 days after purchase and are consumed before next month's quota replenishes. With auto-top-up enabled, the session continues without interruption.

Is typed cheaper than Claude Pro? On Sonnet and Opus tiers, where most production coding lives, the per-token math favors typed. Haiku-equivalent traffic is closer to a wash. See the migration page for the per-tier breakdown.

The shorter version

Rolling windows are a vendor tool dressed up as a billing model. typed's monthly quota + optional auto-top-up moves the control to you: pick whether you want to be interrupted at the cap, set a ceiling if you want one, and never wonder when the next window resets, because there isn't one.

If you want to try it:

curl -fsSL https://app.typed.cloud/install.sh | bash -s <your typed key>

Get your typed key at app.typed.cloud, then t from any project directory.