Claude Code Just Added OpenClaw's Iconic Feature

Let's do a quick video on Claude code loop. It's an amazing new feature that

loop. It's an amazing new feature that previously actually co-work was first to the game with this with their schedule feature and then a week later Claude code brought it in. So what is a loop?

It's a cron job. It's something that repeats on a regular interval. And the

great thing about it is that it literally can do anything that you want.

Whether you're on a code base, it can do coding tasks or whether you just want the daily news. Obviously, the big thing about this is that it needs clawed code

to be running. It can't run in the background, which is in some ways why I like the co-work implementation.

However, you might be having cloud code running all the time. So, how the freak do we do this? Well, you literally just type slash loop and then the next part would be something like natural language

for an interval. Run a prompt/ command or the recurring interval. So, you could run it every 5 minutes. You could run it 9:00 a.m. every week. You could say

9:00 a.m. every week. You could say every hour run bun test or something like this. Now I think one of the most

like this. Now I think one of the most interesting thing is again is why I mentioned that you can run uh any sort of prompt is that you can say go I'm

messing up all my spelling here aren't I 9 a.m. every Monday, get me the latest

9 a.m. every Monday, get me the latest in AI news. And that will now run every Monday, it will run the prompt. And

because it has access to tools and skills and things like this is able just to do things just like you normally would. Anything you can prompt, it can

would. Anything you can prompt, it can do. So, you can see here, I've scheduled

do. So, you can see here, I've scheduled a returning cast to run every Monday at 9:00 a.m. that will fetch the latest AI

9:00 a.m. that will fetch the latest AI news from you. So if I say what scheduled tasks do I have got chron list

here we have one scheduled task we copy the ID delete chron ID and it's been deleted I could have

canceled that by saying uh cancel AI news job and again through natural language it will figure out that we want to actually cancel that cron job. Now,

there is a note in the docs about a 3day expiry. From my understanding is that

expiry. From my understanding is that this basically prevents you running scheduled tasks inside of Clawude Code.

It doesn't want you to keep doing them.

So, I'm not 100% sure what's going to happen with my 9:00 a.m. job because

obviously that's going to be every 7 days. But, they recommend actually

days. But, they recommend actually creating a schedule task inside the desktop app. So, with the desktop app

desktop app. So, with the desktop app here, you've got this schedule feature, which is also available inside of co-work, [snorts]

but not inside of chat. I have a regular interval for checking sponsorship emails. And this runs every single hour

emails. And this runs every single hour and just checks what's going on with my sponsorships and things like this. It's

really easy to set up. You literally

enter a new task, tell you what it wants to do and the frequency in which you want to actually do it. You can even select a default model and a particular folder to work in. Now, one of the

biggest and coolest things that these schedule tasks can do is they can actually run skills. Skills are the backbone to a lot of what I do. And the

great thing about this is that you can run the skill like yourself and you can do them when you want it to be done or you can bind it to a schedule. So I'd

strongly recommend creating a skill of the thing that you want to run first and then binding a or wrapping a schedule around it. So as an example, I've got my

around it. So as an example, I've got my YouTube sponsorships.

If we go to customize here and skills, I've got an inbox triage that looks at the database. uh my looks at my

the database. uh my looks at my sponsorship database and then goes through my emails and tries to bind them all together, try and understand what's

going on and the different processes.

Once I got that working, once I could type slashsponsorship inbox triage and get that working, then I was like, okay, let's now run this hourly, in which I

did do that using the schedule. So in

here, my instruction literally is run the sponsorship inbox triage. This will

just naturally invoke the skill. And to

be honest, I do prefer inside of co-work because if we take one, the the formatting is just a lot clearer than clawed code. However, obviously for

clawed code. However, obviously for coding tasks, I mean, arguably the code tab would also be a lot clearer in its formatting and things like that. Now,

this of course begs the question about open claw and whether this actually can replace open claw. And in my opinion, the setup that I have here where I create a skill and then create a chron

job to wrap around the skill is exactly what I'm doing on many things on openclaw. Plus, I get to use my claude

openclaw. Plus, I get to use my claude code max subscription, which is obviously something they took away from openclaw. But the one big reason why I

openclaw. But the one big reason why I love OpenClaw is that it is running all of the time on a sort of low p or it can be a lower powered device is the fact

that I can actually text it. Um to do something similar on claude code. I'd

have to have a remote control session which I've got a video on here uh to be able to you know interact with things that come top of mind. Um, and so once

I've already got this ability to text an AI and let it know what it wants to do, I may as well lean more into that ecosystem. So the killer feature for me

ecosystem. So the killer feature for me for OpenClaw is the ability to when I'm out and about is to get it to do things for me. That is so powerful and for it

for me. That is so powerful and for it to contact me via text, you know, with updates and stuff like that. I will be doing a video on exactly how I use OpenClaw, a real deep dive. So

definitely subscribe to that. But for

right now, even though I am in clawed code every single day for my work, I still don't think I would be using this loop feature, you know, as a replacement for claw code. I'll absolutely be using

it. Certainly with maybe pushing the

it. Certainly with maybe pushing the code every hour or making sure those tests are run, but as a productivity uh from a productivity perspective, not really going to be using it, I don't

think. Anyway, like, subscribe if you

think. Anyway, like, subscribe if you haven't already. Thank you to my

haven't already. Thank you to my patreons who support me directly.