Here’s the thing I didn’t realize for a while. That five hour window isn’t fixed to a clock. It starts sliding from your first message of the day. So if you open Claude at 10am, your reset lands at 3pm, whether that’s convenient for you or not.

I saw this idea on r/ClaudeAI: send a throwaway message hours before you actually start working, and your reset shifts earlier too. I liked it but knew I’d forget to do it by hand. So I automated it instead.

The setup

Claude has a scheduled tasks feature (routines) that runs on its own, no laptop required.

PROMPT:

Here’s the complete prompt you could give to Claude to set up the same scheduled task:

```
Set up a scheduled task with these specifications:

• Task name: “Hourly hi message”
• What it does: Say “hi” to the chat
• Schedule: Every 5 hours, recurring indefinitely
• Cron expression: 0 */5 * * * (runs at minute 0 of every 5th hour: 12:00 AM, 5:00 AM, 10:00 AM, 3:00 PM, 8:00 PM, etc. UTC)
• Prompt for the task: “Say hi!”
• Model: Claude Haiku 4.5
• Results delivery: Back to this chat (bind to persistent session if possible)
• Initiation reason: human_request
• Run mode: Cloud-based, recurring

Use the create_trigger (or mcp__claude-code-remote__create_trigger) tool with:

• name: "Hourly hi message"
• prompt: "Say hi!"
• cron_expression: "0 */5 * * *"
• initiation: "human_request"

Optional: For results to appear in the current conversation, request the task be bound to a persistent session when setting it up.

```
What it does:

1. Create a new scheduled task. Mine’s called “Hourly hi message.” Name’s a leftover from testing, never bothered fixing it.

2. Give it a trivial instruction. Mine just says “Say hi!” The content doesn’t matter. You just need a new session to start.

3. Repeat it every 5 hours. Match the interval to the window length. Mine runs at :23 past the hour, every 5 hours, every day, in UTC.

4. Time the first run so your reset lands before you need it. I worked backward from my usual start time and set the first run a few hours ahead of it.

5. Set it to always allowed. It’s just saying hi, nothing risky, so I skipped the approval step.

6. Turn it on and forget about it. It runs on Anthropic’s side. Doesn’t care if my laptop’s open.

Does it help

Some, not infinitely. It doesn’t give me more total usage, just better timed resets. I still hit the wall occasionally on heavy days. But it happens less, and the wait is shorter when it does.

One caveat worth saying plainly: this leans on how the reset timing currently works. If that changes, this whole trick stops doing much. Worth knowing before you build your whole morning around it.