Original Reddit post

This might be a weird assumption, and I don’t have enough complete data yet to prove it with proper numbers, but I’ve noticed something consistently over the past couple of months. There seems to be a pattern in how quickly the usage limit gets consumed: The usage limit feels like it drains much faster during the first 1–2 days after the weekly reset. Using the model during working hours, especially in the morning and around noon, seems to consume the usage limit much faster than using it at night, particularly around midnight. Sometimes the usage consumption seems random. It can suddenly drain extremely quickly or, at other times, barely move at all. Even with that randomness, I’ve seen this general pattern happen consistently enough that I started testing it more deliberately. I used the same prompt, the same article link, and the same model of Fable 5.1. The prompt was basically: “Read this article and tell me your findings.” Here are the results I observed:

  1. Morning, on the weekly reset day — around 6:00 AM. The prompt consumed around 45% of my 5-hour usage limit . At the same time, it already used roughly 7–8% of my weekly Fable usage limit .
  2. Morning, around the middle of the week — around 7:00 AM. Using essentially the same prompt and model consumed around 23–35% of the 5-hour usage limit . So it was still expensive, but noticeably lower than what happened on the reset day.
  3. Midnight, on the same reset day This is where it started becoming strange. The exact same prompt that consumed approximately 45% of the 5-hour limit in the morning only consumed around 10–15% when I tested it again around midnight. Same model, same article, and essentially the same prompt.
  4. Around 11:00 PM, three days after the weekly reset This was the most extreme difference I observed. The same prompt using Fable 5.1 consumed only around 3% of the 5-hour usage limit . The weekly Fable usage limit barely moved as well, probably around 1–2% , sometimes even less. There is still some randomness, because repeated tests do not always produce exactly the same percentage, but the results at night are usually somewhere around that range. And it does not seem to happen only with article-reading tests. I notice a very similar pattern when I use the models for relatively simple tasks in Cowork , and especially in Claude Code , which is where most of my usage happens because I’m building things there. When I do most of my Claude Code work at night, my weekly usage tends to last extremely well. On my 5× Max subscription , I can often manage the usage almost perfectly across the entire week and reach close to 100% of the weekly Fable allowance only on the final day before the reset . I’ve noticed a similar pattern with some of the other models as well. In other words, if most of my heavier work happens late at night, the weekly allocation feels much more predictable and efficient. I can work throughout the week and usually get very close to fully utilizing the plan without running out significantly early. However, when I shift that same kind of work to the morning or afternoon , the behavior can look completely different. If I use Claude Code heavily during the morning or noon, especially during the first few days after the weekly reset, the weekly allowance can disappear incredibly quickly. There have been cases where the weekly Fable allocation was already almost completely exhausted, close to 100% used, by around day three . That is a massive difference compared with the weeks where I mainly work at night and the same allowance lasts almost perfectly until the final day. Of course, I understand that Claude Code workloads are harder to compare perfectly than a single fixed article prompt. Different coding sessions can involve different amounts of context, tool calls, file reads, reasoning, code generation, and conversation history. That is why I don’t treat the Claude Code observations alone as proof. But what makes me curious is that the same general pattern also appears when I deliberately test much simpler and more repeatable tasks. So the strange part is that I’m not simply seeing a difference caused by using a more complicated prompt or switching to a more expensive model. I’m seeing substantially different usage consumption while using the same model, the same article, and essentially the same prompt , depending on the time of day and, possibly, how many days have passed since the weekly reset. The broader pattern I keep observing looks roughly like this: Nighttime usage → weekly limit tends to last much longer and often reaches the end of the week almost perfectly. Morning/noon usage → both the 5-hour limit and weekly limit often seem to drain noticeably faster, especially during the first few days after reset. There is definitely still randomness involved, and I don’t have enough controlled data yet to say what is actually causing it. There could be other variables I’m not seeing, such as context size, caching, server-side accounting, tool usage, model routing, or something else entirely. So I’m not claiming that time of day directly determines how usage is calculated. But after seeing this happen repeatedly over the past couple of months, across normal Claude Code work, Cowork tasks, and more controlled repeated-prompt tests, the pattern has been consistent enough that I don’t think I can dismiss it as purely random anymore. So, anyone seeing this pattern too or maybe you found it in a different way? submitted by /u/Brilliant_Film_2426

Originally posted by u/Brilliant_Film_2426 on r/ClaudeCode