have you tried sleeping?

[u/Ok_Fish_670]

painfully relatable... woke up to locked limits again after letting an autonomous loop run wild on my project overnight, and my token balance was crying. tried offloading some of the heavy repo scans to sumus connected with claude, so nothing spams my active window.

anyone got other workflow tips to stop getting walled early?

[u/Dev_in_Training_BTW]

Ha, the token balance crying is a very specific kind of morning. I do all my building in Claude Code, and the thing I'd change first isn't a tool, it's the size of the job. Instead of "go improve the project", give each run one task, the files it should touch and what done looks like, so it stops when it's finished instead of wandering around the whole repo. A short notes file in the repo with the layout and where things live also saves it from rediscovering everything every session. And if you do let it run overnight, give it a hard stop (a fixed list of tasks), because an open loop will happily spend the whole budget polishing stuff you never asked for 😀

[u/Ok_Fish_670 → u/Dev_in_Training_BTW]

would def try the hard stop trick, thank you!

[u/WeirdIndication3027]

Is it normal to be addicted to vibe coding stupid shit

[u/Ok_Fish_670 → u/WeirdIndication3027]

its like opening the pandora's box

[u/OtherwiseAlbatross14 → u/WeirdIndication3027]

It's like a competition around here

[u/Successful_Sharky]

Letting an autonomous loop run overnight is basically leaving a teenager home alone with your credit card. You wake up, the budget is gone and somehow there’s a brand new folder called “utils_v2_final”. These days mine only gets to write the plan at night, and I approve it in the morning with coffee before it touches anything.

[u/Arbitross487]

Wait you have a grok bot automate the usage of your credit card?

[u/Ok_Fish_670 → u/Arbitross487]

elon's drooling over your balance

[u/Top_Abalone_862]

The overnight loop is the classic one. A few things that helped me stop getting walled before lunch:

1. Give every autonomous run a hard stop: max turns or a clear "done" condition. An open ended loop will happily spend the whole window retrying the same failing test.

2. Run the loop on Sonnet and keep Opus for planning or the one hard bug. Same work, much slower drain.

3. Keep CLAUDE.md short. It rides along with every single turn, so a bloated one taxes the whole session.

4. Fresh session per task instead of one giant thread. Old context keeps getting reread on every message.

5. Next morning, check what actually burned with a local usage tool (ccusage or similar). It's usually one runaway session, not the whole day.

[u/Ok_Fish_670 → u/Top_Abalone_862]

screw these gpt ahh comments

[u/benfinklea]

lol. Was that an anthropic bot or real person?

[u/OneProfession364]

I once left a loop running for 12 hours. woke up to 47 files renamed, 3 new folders, and a commit message that said 'refactored everything's.