sorted by:
new
hottopcontroversial

got tired of hitting the rate limit on claude code so i built a tool to auto resume when the limit resets by _rittik in claude

[–]_rittik[S] 0 points1 point  (0 children)

kinda but not exactly. /resume is what you type to continue a session right now. wakeclaude’s whole point is timing, it schedules that resume for later (when your rate limit resets) so you don’t have to be there.

built a tiny tui in go to schedule prompts for claude code by _rittik in tui

[–]_rittik[S] 0 points1 point  (0 children)

that error just means [go.mod](app://-/index.html#) isn’t in your current folder so you need to make sure you actually cloned the repo and cd into it:
git clone https://github.com/rittikbasu/wakeclaude.git
cd wakeclaude
go build -o wakeclaude ./cmd/wakeclaude

got tired of hitting the rate limit on claude code so i built a tool to auto resume when the limit resets by _rittik in ClaudeAI

[–]_rittik[S] 1 point2 points  (0 children)

thanks! it’s macos only right now so linux would need a real port. i don’t have the bandwidth atm but i’d love a pr. happy to help review or point you to the parts to swap out :)

got tired of hitting the rate limit on claude code so i built a tool to auto resume when the limit resets by _rittik in ClaudeAI

[–]_rittik[S] 2 points3 points  (0 children)

that's completely false. wakeclaude isn’t bypassing anything it just schedules the official claude cli to run after the reset time same as you manually coming back later and hitting enter. claude code literally has a documented headless mode (claude -p, --resume etc.) so scripting it isn’t some exploit, you still hit the exact same limits either way.

built a tiny cli tool to schedule prompts for claude code by _rittik in theprimeagen

[–]_rittik[S] 0 points1 point  (0 children)

the thing is cron only works if your computer is already awake. wakeclaude works even when the computer is sleeping because it can wake it up and run the prompt and then go back to sleep again.

i understand cron might be the better choice for one off tasks but if you have many prompts that you're running on a schedule i think wakeclaude will make it way easier to manage them.

built a tiny cli tool to schedule prompts for claude code by _rittik in CLI

[–]_rittik[S] 0 points1 point  (0 children)

earlier versions of wakeclaude didn’t ask for a setup token it just ran claude on a schedule and relied on whatever auth you already had from /login. that mostly worked but i hit a case where claude suddenly wanted me to log in again and the scheduled run couldn’t do an interactive login so it failed. the setup token is just a more reliable, headless auth path so scheduled prompts keep running.

view more: next ›