Claude Code Routines

“Claude Routines/Scheduled agents can replace all the tasks I use OpenClaw for”

“I couldn't think of anything useful to do with the routines”

“It's almost too easy to spin a new one up.”

“A Claude Routine would've been significantly easier”

“major vendor lock-in + hazy perspective”

“Now use it less and use more Claude Code Remote Routines”

“The trigger matrix here is actually the most interesting part.”

“Once setting the cron job itself is free, you could think of a lot of use cases.”

“I tried routines and they didn’t actually work.”

“moving your tech debt into a proprietary format”

“That's all this "routines" thing is, it's just an agentic loop they launch in their cloud on a timer.”

“you only have one at a time per suscription”

“90% of the time the automation never even runs.”

“I never want to outsource something so simple to a live service.”

“there is a limited way to configure it with other models”

“throw sh*t at the wall and see what sticks”

“It was a bit buggy, but it seems to work better now.”

“I have no qualms using a convenient feature I could reimplement myself, it saves me time.”

“This is a smarter, faster, easier, and likely far more secure way of implementing the same thing”

“But when I try to create a routine, the only GitHub events available in the drop down related to pull requests and releases.”

“The cap of 15 automatic Claude Code Routines runs per day is a bit low.”

“Friction. That's all it takes to lock users in.”

“it's something that keeps you from ever switching off Claude”

“There is no reason to believe Co-work/Routines/Skills will survive 5 years from now.”

“I love this feature very much, when it works. And it mostly doesn't.”

“you shouldn't bother using /loop, code routines, etc.”

“Now they’re trying to back track that with a cloud solution.”

“This is useful functionality but also seems very straightforward.”

“Buying in to things like this would make that much harder.”

“I wish they'd release more stuff that didn't rely on me routing all my data through their cloud to work.”

“This wild, one of the pieces I was lacking for a very openclaw-esque future.”

“vendor specific, "bonuses" sounds like a way to try to lock people in”

“The Chilling Effect of this is real and it gets more and more frustrating that they can't or won't clarify.”

“7 days is long enough for work to leave the context window”

“Very useful, (when it works).”

“Why would you use it if you don't know whether the model will be nerfed at that run?”

“any way to organize and control these at an organization rather than individual level”

“Seems like it only supports x86_64. It would be nice if they offered a way to bring your own compute”

“the $200/mo subscription is markedly cheaper than per-token API billing”

“at the end of the day this is yet another way of injecting data into a prompt”