# Why idle Claude accounts waste their 5-hour window > Claude's 5-hour window only starts when you use an account, so an idle one wastes time. Shuriken starts its clock with one tiny background request. Source: https://shuriken.sh/blog/the-5-hour-clock-starts-when-you-do Claude's 5-hour window only starts when you use an account, so an idle one wastes time. Shuriken starts its clock with one tiny background request. Story By Shuriken Updated 27 October 2026 4 min read **Contents** An idle Claude account isn't saving anything for later. Its 5-hour window hasn't started, so it can't reset either. Switch to it at 4 pm and its limit comes back at 9 pm. If it had been used once at 9 am, it would have been fresh again by 2 pm. So Shuriken starts idle accounts' clocks for you, with one tiny request each, under rules we hold ourselves to. ## How Claude's 5-hour window works # Anthropic's help center says paid plans have two kinds of limits: "a session limit that resets every five hours" and weekly limits that reset once a week ([Anthropic, read 22 October 2026](https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work)). Under Settings › Usage, Claude shows how much of the session limit you've used and "the amount of time remaining in the session" ([Anthropic](https://support.claude.com/en/articles/9797557-usage-limit-best-practices)). The window isn't pinned to the clock on the wall. Not midnight, not the top of the hour: it starts when you start using the account. Anthropic's earlier help article on Max plan usage said so directly (a session starts with your first message). That article has since come down, and the current pages don't spell out the start, but it matches what Shuriken reads from every account. One nobody has used yet shows 0% and no countdown, because nothing is counting down. (More in our [guide to the 5-hour limit](https://shuriken.sh/guides/claude-5-hour-limit-explained) and on the [weekly limit](https://shuriken.sh/guides/claude-weekly-limit-explained).) ## Why that hurts with more than one account # With one account it barely matters. With two or three, it costs you hours. Say you have a Work, a Personal and a Side account. You start at 9 on Work. At 11:30 Work is nearly out, so you (or Shuriken) move to Personal. Personal's clock only starts now, so it resets at 16:30. Side starts at 14:00 and resets at 19:00. Each account was available all morning. Two of them just sat there without their clock running. By the time you need them again, they're hours from coming back. ## The idea # When an account's 5-hour window isn't running, send it one tiny request, so its clock starts. That is all it takes, because the window starts on first use, whatever the use is. In the example, Shuriken sends Personal and Side one request each at 09:00. Their windows run from 09:00, like Work's, and all three come back at 14:00 instead of 14:00, 16:30 and 19:00. Your chats don't move to do it. Work carries on until it reaches your switch point, and then [source switching](https://shuriken.sh/features/source-switching) moves your chats to an account whose window is already counting down. Those times are an example, not a measurement; yours depend on how fast you work and how big your plans are. What carries over is the shape: a window that starts early comes back early. Shuriken moves a running chat to another of your own accounts when one reaches its limit, on every device. [Try Shuriken](https://shuriken.sh/) ## The rules we hold to # Our first version started clocks with your real work instead: while the account you were on still had room, it moved your next turns to an idle account. That made switching hard to follow, because a chat could change account for a reason that had nothing to do with its own limits. On 24 October 2026 we replaced it with the request. A request that starts a clock still counts, so we keep it small and rare. - One request per window. After a request goes through, that account is left alone until its window resets. One that fails waits 10 minutes before the next try, then longer each time, up to 4 hours. - The smallest model, nothing kept. The request is "Hi" to the smallest model, with no tools, and its short answer is thrown away. It never shows in a chat, your history or Activity. It does count toward that account's usage, like any request. - One computer. Only the computer that holds the account's sign-in sends it, so two of your devices never start the same clock twice. - Subscriptions only. API keys have no 5-hour window, so they're left alone. - Your weekly limit counts. An account past its weekly switch point is skipped. Starting its clock would only spend a week you're trying to save. And one thing it doesn't do: give you more usage. Your weekly limit is the same. 5-hour clocks change when your 5-hour windows come back, not how much is in them. ## What you notice # Most days you won't notice anything. When the account you're on runs low, the next one has been counting down since the morning, so its limit comes back sooner, and [source switching](https://shuriken.sh/features/source-switching) moves your chats there by itself. If you're curious, every account's 5-hour and weekly use sits side by side in Sources, and pointing at a bar shows when it resets. ## Where to find it # It's on by default. The setting is called Start unused session limits, under Sources › Switch settings, and it works whether or not automatic switching is on. Turn it off if you'd rather start each account's window yourself. The [5-hour clocks page](https://shuriken.sh/features/session-clock) has the full picture, and if you're already stuck, read [Claude usage limit reached? What to do next](https://shuriken.sh/guides/claude-limit-reached-what-to-do). Use only accounts you own and are entitled to use. Providers' terms may not allow sharing a subscription sign-in. If you have more than one Claude account, their clocks should be running. [Try Shuriken](https://shuriken.sh/) and they will be. Try the free tool: [Claude limit reset tracker](https://shuriken.sh/tools/limit-resets/claude) Share [X](https://x.com/intent/post?url=https%3A%2F%2Fshuriken.sh%2Fblog%2Fthe-5-hour-clock-starts-when-you-do&text=The%205-hour%20clock%20starts%20when%20you%20do.%20So%20we%20start%20it.)[LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fshuriken.sh%2Fblog%2Fthe-5-hour-clock-starts-when-you-do)[Hacker News](https://news.ycombinator.com/submitlink?u=https%3A%2F%2Fshuriken.sh%2Fblog%2Fthe-5-hour-clock-starts-when-you-do&t=The%205-hour%20clock%20starts%20when%20you%20do.%20So%20we%20start%20it.)[Reddit](https://www.reddit.com/submit?url=https%3A%2F%2Fshuriken.sh%2Fblog%2Fthe-5-hour-clock-starts-when-you-do&title=The%205-hour%20clock%20starts%20when%20you%20do.%20So%20we%20start%20it.)[E-mail](mailto:?subject=The%205-hour%20clock%20starts%20when%20you%20do.%20So%20we%20start%20it.&body=https%3A%2F%2Fshuriken.sh%2Fblog%2Fthe-5-hour-clock-starts-when-you-do) ## Sources - [Claude Help Center: How do usage and length limits work?](https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work) (accessed 22 October 2026) - [Claude Help Center: Usage limit best practices](https://support.claude.com/en/articles/9797557-usage-limit-best-practices) (accessed 22 October 2026) ## Frequently asked questions **Does Shuriken send messages just to start the clock?** Yes, one tiny request per window, to the smallest model, from the one computer that holds the account's sign-in. It never shows in a chat or your history, and it counts toward that account's usage like any request. **Does this give me more weekly usage?** No. Your weekly limit stays exactly the same. What changes is when each account's 5-hour window comes back, which is earlier. **Does it work with API keys?** It doesn't need to. API keys have no 5-hour window, so 5-hour clocks only apply to subscriptions. **Where do I turn it off?** In Shuriken, open Sources › Switch settings and turn off Start unused session limits. It's on by default. **Is it allowed?** It only uses accounts you added, through their own sign-in, from your own computer. Use only accounts you own and are entitled to use; providers' terms may not allow sharing a subscription sign-in. Source switching One account runs dry. The next one takes over. Add the Claude, Codex and Gemini accounts you own. At your switch point, your chats move to another of them and keep going. [Try Shuriken](https://shuriken.sh/) [How it works](https://shuriken.sh/features/source-switching) ## Keep reading - [We were tired of logging in and out of Claude: Story 27 Oct 2026 3 min read Limit reached, /logout, /login, paste the context back. We did it so often we built Shuriken: chats move to an account with room by themselves.](https://shuriken.sh/blog/why-we-built-shuriken) - [Hot swapping: chats that move when an account runs out: Story 27 Oct 2026 4 min read Hot swapping AI accounts, the way Shuriken does it: your running chats move to another of your accounts when one nears its limit. What happens at 99%.](https://shuriken.sh/blog/hot-swapping-accounts) - [How Shuriken picks the next account: Story 27 Oct 2026 5 min read At your switch point (99% by default) or a limit, Shuriken moves your chats to the source with the most room. Expiring capacity goes first, API keys last.](https://shuriken.sh/blog/how-switching-picks-the-next-account) - [Every plan and key you own, working as one: Story 27 Oct 2026 4 min read Add your Claude, ChatGPT, Gemini and other plans and API keys to Shuriken as sources. When one runs out, your chats move to the next.](https://shuriken.sh/blog/what-is-a-source) - [Codex with more than one ChatGPT account: Update 27 Oct 2026 4 min read Add each ChatGPT sign-in you own as a source. When one reaches its Codex limit, Shuriken moves your Codex chats to the next and they carry on.](https://shuriken.sh/blog/codex-multiple-chatgpt-accounts) - [Distribute: spread work across accounts on a clock: Update 27 Oct 2026 4 min read Two modes: Rotation moves your chats only when an account runs out; Distribute moves them every 15 to 60 minutes to the one with the most left.](https://shuriken.sh/blog/distribute-mode) - [Shuriken is officially launched, in beta: Story 27 Oct 2026 5 min read The harness for Claude Code, Codex and other coding agents is open to everyone. It began as our internal tool; here is what it does and what beta means.](https://shuriken.sh/blog/shuriken-is-now-in-beta) - [Bring your own plans: we never bill model usage: Story 27 Oct 2026 3 min read Shuriken runs Claude Code, Codex and other agents with your own subscriptions and keys. We never resell tokens or add a margin.](https://shuriken.sh/blog/we-dont-bill-model-usage) ## Free tools - [Claude limit reset tracker](https://shuriken.sh/tools/limit-resets/claude) - [Codex limit reset tracker](https://shuriken.sh/tools/limit-resets/codex)