Five-Hour Temple

五小時宮 · RATE LIMIT ORACLE

Ordinary people pray for money and marriage.
Engineers pray for quota.

THE READING
What you seek
The traveller
Lost item

Draw a bad one and you may ask again with the moon blocks.
The deity will reconsider. Your quota will not.

Free. No offering required. Shake until satisfied.

NEXT RESET  --:--:--

All nine fortunes

Every line below is a message that has genuinely appeared — in the Claude Code terminal, on claude.ai, or in an API response.

  1. No. 1 · Moderate blessingApproaching usage limitThe red text appears in the corner. This is a warning, not a punishment.
  2. No. 7 · MiddlingYou are out of free messages until 9 PMThe free tier lives in someone else's house. Nine o'clock is still today.
  3. No. 12 · MiddlingYour limit will reset at 3pm (America/Santiago)An afternoon in Chile is not your afternoon. Wrong timezone, wrong life.
  4. No. 19 · Great misfortuneOpus weekly limit reached ∙ resets Oct 6, 1pmFive hours is a small gate. A week is a large one.
  5. No. 23 · MisfortuneYou've hit your usage limit.Six words. No reason given, no room to argue.
  6. No. 30 · MisfortuneAPI Error: Rate limit reached · 429Subscription and API share one sentence, so nobody knows the cause of death.
  7. No. 36 · Moderate blessingTip: Long chats cause you to reach your usage limits faster.It warned you already. This is not a punishment, it is an echo.
  8. No. 40 · Misfortune/upgrade to increase your usage limitThis is not a fortune. This is an ad. The deity is holding out a hand.
  9. No. 49 · Great blessing(no message — quota intact)A clean screen, no red text. Great fortune, and it will not last.

Three questions people keep asking

How often does the limit reset?
Subscriptions run on a rolling five-hour window that starts with your first message. A weekly cap sits on top of it, which is why a reset time occasionally lands several days out. That is the weekly cap, not a bug.
Why did chatting on the web drain Claude Code?
claude.ai, Claude Code and Claude Desktop all pull from one account-level allowance. Whichever surface you use, it is the same bucket.
What can I actually do about it?
Switch to a lighter model, start a fresh conversation to cut the context, or wait. Developers can move to pay-as-you-go API usage. Shaking the tube does nothing, but it beats staring at the clock.