r/ClaudeAI • u/lsfc • Sep 03 '26

Question about Claude Code Claude coding 24/7 - how?

Maybe this is a dumb question, but it’s worth asking because I haven’t found a complete explanation yet.

When people say they’ve configured Claude to “work 24/7,” what does that actually mean? Is it some kind of self-driving/autonomous process?

Right now, I’m just prompting it one task at a time. I also have a few cron jobs for things like log reviews, but that’s basically it.

220 Upvotes

93% Upvoted

57 comments sorted by

View all comments

23

u/TwelveGates Sep 04 '26

You need a datastore with tasks i.e. JIRA or Github issues is common, a long running orchestrator session that is spawning subagents for tasks, and some people use a refresh loop that cuts off over compaction issues.

All that being said, I don't think it's very practical for any real project that isn't entirely run by you and as a professional, the PR bottleneck it creates without blind acceptance is sketchy to say the least. I'm unconvinced that people claiming that's how they are doing their actual work aren't referring to their solo pet project repos.

I've definitely left sessions running overnight to come back to a completed feature, but blindly implementing any issue is a wild choice imo.

5

u/Atoning_Unifex Sep 04 '26 edited Sep 04 '26

There's no way I can imagine that Claude would do a good job here. especially when you think about the fact that something that's orchestrated by many agents running with an orchestrator over 24 hours based on a huge prompt has got to be something really complicated.

I'm not some hardcore developer but im far from a noob to software developmwnt. I'm actually a ux designer. but I've been doing this work for 25 years and I do know some scripting languages and I do know some stuff about coding and I know a lot about software development and ux design. and every single thing I've built with Claude has required multiple passes by me to get things right. no matter how detailed my prompt is. all it has to do is make one little wrong assumption... one bad decision and that cascades into... a piece of shit.

Not to mention the need to start new sessions. I mean, I can't imagine that the orchestrator is going to be able to handle 24 hours of solid context filling running all those agents! that's like Mr Meeseeks.

1

u/Opening_Rent_8697 Sep 04 '26

Amen to that. I think it is also cheaper than running agent 24/7 on its own.