Run OpenClaw on Workers

Hey, hey, welcome everybody. We got together today because there has been some very interesting stuff that happened. I kind of missed out. I missed out on something pretty big. I've been seeing these news headlines flash through, and I brought on some experts here to talk today to us. I would love for you all to meet both Sid and Andreas, and I'm going to do the thing that all hosts do where I say, Hey, how do you introduce yourself these days? Sid, what, what is, let's start with you Sid. Sid, how do you introduce yourself these days? What's up Craig? Well, my name is Sid. I work at Cloudflare. I've been here about four years. Yeah. I work on workflows mostly, but this has been a fun sort of experiment on the side. Awesome. And Andreas, please, please tell us, tell us what, what, what is it that you do here? I'm new here. I just joined in December. I used to be a co -founder at Replicate. That's just got acquired and we're still working on Replicate, but sort of got pulled into this Moldworker open core thing and had a lot of fun with that for, for a couple of weeks now. Awesome. And Andreas, I've been a fan of yours for so long. I can't believe that we haven't ever had one of these before that we haven't actually chatted with. I'm so excited. This is going to be super exciting for, for everybody watching at home. And so I want to talk a little bit, so I'm a developer educator. I think that like what just happened with this, I love to hang out in the AI space. I was at a conference. I was at basically a two week conference and I missed it all. And I saw y'all having fun and I need to get up to speed with, first of all, like what, what in the hell just happened though? Everything went wild for a while. It's for a bit here. So, so people were out buying things and people were running and trying to figure. And this craze really took off. And can we, can we put this all together? So it's, I don't want to get in trouble because I think that like, we could probably say the old name of it. But it had to change because of legal reasons, the, the original name, right? Do you remember what that, what, what was the original name of this thing that were, I'll take one for the team. Okay. Claude bought and then it got, but not, but not C L a U D Claude bought with a claw. So that was C L. So we've got, we've, oh, claws. And Malt, Malt is who, which one of you knows what that means? What, why is never heard the word for Andreas? I don't know. I'm not the native speaker. From my understanding, it has something to do with what happens to a lobster. So, so they're, they're, they're really leaning into the claw. They got in trouble, right? Because Claude sounds like you can't say Claude. It sounds like the other thing, Claude, right? The anthropoclaud. And so, so, so, so, so, so, so, so, so, so, so, so, so, so, so, so, so, so, so, so, so, Malt is something that happens to lobsters, but I don't think anybody knew what that was. And then it became, I actually liked the new name. It's called open claw. Open claw. Right. Okay. I like it. It's better than, I think I like it more than Malt bot for sure. For sure. I sounded like some sort of wizard thing. I was like, what is this other thing that's happening? And why is it also a crab? And it's like, oh, it's the same thing. So it's very hard. Yeah. They like them all stuck around, right? People still refer to it as, as Claude bot and then Malt book happen. And then like Malt is forever stuck with that. So yeah, I mean, I'm not, you know, I wouldn't blame anyone for calling it the old names. Yeah. So, so what, what is it? Why, why is every, so, so what, first of all, what, what is it? What's going on here in general? What is open claw? Well, it's, it's an agent, right? But it's an agent that has, that has claws, which, which was the sort of the original naming. It has, it has like effectively like, you know, sensors and actuators. It has, it can, you can talk to it in your telegram or WhatsApp or signal messages app. And then it can just like do anything really. Like, you know, people give it access to their emails and their calendars and Google flights or whatever. And it can, you know, do your whole schedule. People give it access to their fridge, you know, like the, the whole, the whole sort of IOT space. It's kind of crazy, man. I don't think I can access my fridge. What fridge are you using? It's not my, it's not my fridge. No, but yeah, I think, I think that's kind of, it's, it's like one of those things, like when the iPhone came out, everyone's like, well, you know, I have my own, like, you know, Nokia, whatever it can, I can send messages. But I think, I think the nice thing with, with open claw is the way that they just packaged all of this together. So you like, you don't have to, you know, write a bunch of MCP servers and stuff to make it work. It just kind of worked all out of the box. So do you think that it's, is it because it's also the time, I feel like we just recently hit this like place where literally everybody I know is now finally leaning into using coding agents at least. Right. So agents have are like, aha here. It's like, I feel like in November happened. Is this just a, is this a timing thing or is there something like really special about this? No, I'd say I'll quickly jump in. I think what happened, and I suspect all of us had the same experience, at least for me was that December 25th happened, which is when Oh, was it November 25th when the new Opus 4.5 came out and Sonnet 4.5 came out. And I think between that time and Jan, I was out on holiday for a bit. And on holiday, I think we were all playing with Claude code and then open code. And that just completely dramatically shifted what my experience is day to day at work. Like, yeah, so I think everybody, and I think those couple of weeks there is when things got real for us, right? Like we'd used AI models before, but suddenly you could have these AI models running on your machine to, you know, go search the web or like figure out how to fix a bug and fix it for you. And it's obviously been a very fast moving space. It's hard to keep up. But I think what Peter, the author of Open Claw, Peter Steinberger, I hope I'm getting his name right. I don't think it's Steinberger, but I do think it starts with an ST, but you added a burger there. I understand what time of day it is. Oh, well, anyway, Peter, Peter Open Claw, right? He's a Peter Open Claw, Mr. Open Claw, Mr. Open Claw, who's an absolute legend. I think what he did really, you know, I think what's really interesting about Open Claw is that you take all these primitives that people have used, you package it together. And everybody had the same question of, hey, I have open code running and it's great, but I kind of want to talk to it when I'm out and about on my phone, you know, when I'm walking the dog or when I'm cooking, I kind of want to keep track of what my agent's doing. And I think this has been the first sort of, you know, accessible proof of concept slash project that does that. And it does it quite well, I'd say. And Andres, that's because you were talking like Telegram is the way or WhatsApp or text messages is kind of how the there's this new chat flow that's happening there. Yeah, you talk to it like in your existing chat app. I think the social element is really interesting as well. Like I had this is really kind of, I don't know, it was a bit of sort of a eureka moment when Sid and I were playing around with Maltbot and we connected it to Slack. And all of a sudden I could see what Sid was saying to the agent, because before that, like agents to me have been this kind of, you know, it's I have my personal agent that I talk to. But now I can see how Sid interacts with it. And now we can kind of learn the patterns he's using to talk to his agent. And that that's a new thing for me. I think that's I think there's something really powerful in that that's kind of under explored. Yeah, it's cool. Yeah, go ahead. Go ahead, Sid. I think to that point, what Andres just said, we were messing around with this. And we had it was funny, because when we started, we'd barely come out like three days ago, whatever, right. And we knew nothing about it. And we spent a whole day playing with it. And it was so much fun just to sort of be able to say things like, Hey, can you, you know, get can you generate a video of me scrolling on agents.Cloudflare.com, make sure you close the cookie banner. And then I'd say that and you'd get a response from the bot on Slack. And then Andres would want to, you know, do some more with it. And he talked to it. And it was it's the first time it sort of felt real in that you can have an agent on your existing systems and pretend like it's a new coworker. So I think that's been really wild. Since it's only been a couple weeks. How does how did that feel? Can you remember? Can you can you bring bring people into how that actually feels? Because I think that like, for me, there was this like whole wild like people were going out and like literally buying things to play with this because they saw something happen. Can you capture I mean, you did just capture that a little bit, but like capture what that felt like? Yeah, it was I mean, it was honestly very impressive. I knew about the primitives. I knew that the primitives worked with open code, like on my machine, because I've been using that for about, you know, a few weeks then. And I knew how well how good these frontier models have gotten. These SOTA models have gotten at at tool calling and being able to sort of write stuff and figure things out. But it felt very real. It sort of felt like a big shift in that. Okay, now we figured out how to take that and get to like 100x by like, you know, sort of plugging things in. Because I know before that MCPs were all the hype, right? Before right rules and, and before before these LLMs got really good at calling these tools on your CLI. And MCPs were great. But, you know, you still had to do the work ahead of time to make them discoverable and so on. But with this that Eureka moment for me was, I still remember I sent a message about we were trying to set up browser rendering with CloudBot. I'm sorry, OpenClaw. And before we had, and it didn't know I wanted to use browser rendering. I mean, the chap installed Chromium on a sandbox and decided to install Playwright and then go get, do you know what I mean? So like, yeah, made those decisions, actually executed them and got to completion, which was wild to me. Awesome, right? Yeah. And by the way, people have been using this for way more interesting things. I've seen Twitter. I mean, I don't know how much this is true. But on Twitter, I've seen people use this to make restaurant reservations. Apparently someone like tried to and they claim it worked where they would try to make a reservation and couldn't do it on OpenTable. So then it made a phone call and use some other model to like level up and actually made a reservation on the phone. And that's insane. Like, I think that's like, that is what we think of when we think of AI agents, right? At least in science fiction. Yeah. Andres, what's your, what's your moment? Let's, let's actually, let's, let's flip it the other way. Have, and this is, this, this might be really hard to, because what I'm, what I'm hearing is that I haven't been able to stump it. Like, have you had, have you run into a place where like, it doesn't do what you're trying to have it do? Cause I think that's part of it too. It's like the frustrations kind of gone. Yeah, yeah, yeah, yeah. I mean, it's, it's, it's the same sort of frustrations as when you're using open code, you know, it feels like, like the claw analogy is really interesting because it feels like we had this little kind of nurtured lobster without any, any, any append, appendages, is that the word? And then, and then we gave it those appendages and it turns out that like it could control them really well, but it still breaks and, and, and hallucinates and all of, all of those things say the same way that, that claw does in clawed code or open code. Right. Yeah, but what's exciting is that this is, well, I suppose the first one and it's only going to get better from here. Right. Exactly. I would fully expect OS's to have this sort of stuff built in hopefully soon, right? Like I would expect macOS and the new C with Gemini, et cetera, to just do these things for you. Yeah, yeah, yeah. It, it kind of like there's, there's something, you know, I'm, I'm like a hardcore sort of Emacs user and there's something about OpenClaw that, that just reminds me of those old Lisp machines that people used to run, right? Where you could just like, you know, redefine the OS as you were running it. And the fact that OpenClaw has access to its own code and it can restart itself. Oh, wow. You can just like, you know, you can give it an API key and say, here's an API key for this service. And then it'll sort of put that in the right place on the file system, restart itself, and now it has access to this thing. So it's almost like a self evolving thing, you know? I think that's another of those really, really clever thing that Peter did. Like, I think that, that and the heartbeat is a really interesting feature as well. You can run stuff on a cron, you know, you can say like every morning I want, I want a new idea for breakfast or something. And it'll just, it'll just ping you on your phone every morning. Just kind of wake itself up rather than everything being kind of a turn-based conversation. Oh, it's got push instead of pull. Yeah, exactly. Nice. So there are a few little magical things in there. And porridge, like every morning. No, I mean, I, one more really quick example is I remember like to Andreas's point, and then Andreas was doing this and I was watching on Slack. It was great to see. Now he built Replicate and you know, he was showing me a lot of stuff on Replicate and other models on it to sort of generate images. And he started out by asking it to use some models on Replicate and it didn't know how to. So, you know, set back that, Hey, I don't know if I have a token. And obviously it was just a private Slack. So Andreas sent the report, the token on Slack, and then it figured out the rest. It like discovered the APIs online, set up the token for itself, persisted it to disk. And then lo and behold, he was using a bunch of Replicate pipelines to generate stuff over Slack after never having sort of installed a skill or setting up an MCP or having to like go to the, you know, do you know what I mean? There was no, there was no integration. The integration was telling the bot to use it and figure out how to. Cool. Cool. And I imagine, Andreas, I imagine that just because you've been in the space for so long that you're skeptical, but I've, the skepticism here seems like it's gone. I'm excited. Yeah. There's this mode in Cloud Code called, well, I can't remember the name of it, like allow everything or something. Like I've been doing that since, yeah, I've been doing that since like Cloud 3.7. Okay. I love, you know, it hasn't broken anything yet, really. Okay. Awesome. Awesome. Yeah. I do that not on my work machine, but I do that on my personal machine. Note to editors in the future, please remove that wing. Awesome. So, so, so, okay. So this thing's out, people are like raving about it and they are literally going out and buying Mac minis, which I guess still exists. I was like, oh, those things are around still. That's cool. People are buying these things and they're buying them. Why are they, why are they buying them? Why are they buying these Mac minis? I couldn't follow. All I saw was like, oh, there's Sunil just bought one. Oh, there, Confidence bought one. But why is everybody buying these Mac minis? What is happening? So what, what was going on? Why, why a Mac mini? It's, it's just so that you can keep it running in the background. Right? So while, while you're going for a walk, you have this thing that's always on. So, you know, if you're, if you're taking your computer with you, you have this thing, this thing is, it's just personal server, a Mac, just because it can, then you can, um, connect your iMessage app, that's how it's, oh, okay. It's doing some remote control stuff on the Mac. Yeah. Yeah, absolutely. I remember talking to Sunil about this and, uh, briefly, I think it was on Twitter or somewhere. And I think the Eureka, the other Eureka moment was if you have it on a machine that you already use, which is signed into your iCloud, it now can just work with, because Peter did a really smart thing by building in some cases, like, you know, homegrown CLIs when he needed to using Apple script and whatnot, if I remember correctly. So it could just access everything on your machine between iCloud drive and messages and phone calls. And I think that's where the magic is, right? Sort of, you can have agents running somewhere else, like Cloudflare. And of course there's an entire host of security considerations and whatnot, which I don't want to get into just yet, but running it on your own machine means it has access to everything you normally have access to. So you can tell it to look at your notes. Right. And look at your messages, you know, for. Gotcha. Gotcha. So people are building like their own little, they're using that as like their own little cloud, like notes. They're all little Mac apps. They're, they're talking inside their Mac apps. That's kind of what, and, and it can run at all times. You can go and hit that at all times. So you guys are thinking about this and you're like, well, we have a serverless platform. Okay. So you get nerd sniped and you're like, what would this look like if we did it here, right? I'm guessing. I've seen both of you get nerd sniped in the past. I'm assuming you're like, we could do this, right? Like we can run this here. There was like a spiral of nerd sniping going on there one morning with Sid and I were talking. I call it nerd sniped driven development. I feel like half the stuff I do now over the last couple of months has just been to someone said, Hey, can you do this? Like my boss and a manager sells. So we'll often, I'm not even kidding. Say things like, I bet you can't do that. And I'll be like, okay, sure. And then I'll do it over the next two hours. And then he'll, he'll, you know, he'll, he told me about how that was exactly the plan. But yeah, Andreas and I were talking a lot. Because, you know, about AI and agents and so on. And it came in from one of those conversations. Andreas, do you want to, do you want to talk about that? Yeah. What was it we were talking about? We were talking about a lot of things. I think, I think it was the morning when Claude Bot had taken over Twitter and we were talking about this and, you know, like, why are people buying Mac mini's like, you know, there are, there are, you know, computers in, in the cloud that you can run these things on. And we were talking about running this on Cloudflare and what are the sort of the primitives you need to do that? And we kind of mapped it out and it's like, this doesn't sound too, too hard. But then I think what happened was that there was someone else at Cloudflare had the exact same thought, Brian, exactly. And he, he had built a proof of concept that day. And then we sort of all kind of found each other and created a little group to just hack on this and see if we could just like get something working. In a day or two, we got, I mean, it's, I think this is like a big disclaimer here. Like this is not a product. Yeah, right, right, right. Yeah. This is, this is just like a hacked together, a little prototype just to see if it worked. And what kind of Cloudflare primitives you would use to build something like this. You know? Yeah. My like goal with this was, okay, if we can nerd snipe someone else into building something that's like native on Cloudflare here, then, then we've succeeded. Yeah. Yeah. I'm going to bring up something in the comments that said this. They said that they're, they're ready to consider open call on Cloudflare. The key seems to be scanning for malware infected skills is, are we, and maybe this is, this was, are we, are we thinking about including any cybersecurity features? Right. So these malware skills, exactly where my brain first went was like, oh man, someone's going to take advantage of these poor Mac minis. Right. That someone, someone's going to, someone's going to get in there and yeah. Is, is there like talk about using the, the so, so you just, you just very specifically said that this is, this is a proof of concept, but like, are we thinking about taking that farther so that we could show how we might do that? Might, might weed out bad skills or I don't even, I don't even know what that looks like in this case, how do you define bad? Yeah. I mean, just for everybody in the room who, who doesn't know what we mean by weeding out bad skills. I think the, the sort of explain it like I'm five version is that skills are, are Markdown files. Markdown is really exploded, hasn't it? Anyway, it was a Markdown files that describe how to do a new thing, right? And that could include stuff like there happens to be a binary called X and just use that when you need to do something, you know, to authenticate on something or whatever, like Cloudflare D. Um, some skills can potentially include, you know, telling your agent to do things that you don't want to do. Like install a keylogger every time the user types about anything and send it there or whatever. Now to answer the question, that's what, that's what skills are, by the way. And that's how they can be malicious. I mean, it's not hard to do. We could do one right now, but to answer the, the original question to echo Andrea's point, this was a technical showcase because when someone built something like this for the first time. I think there's a lot of value in, in trying it out, building it on us, et cetera, et cetera, to sort of inspire and learn what it would take to build a better version, for example. Not that I'm suggesting we'll be able to, I mean, who knows? And I know the agents team at Cloudflare has been doing this thoroughly. Um, I'm guessing that's something like this is probably on their mind. I wouldn't know. It certainly isn't on my mind. And I don't think we've thought about that at all for this proof of concept. What we have done security wise, which I'm actually quite pleased about is. In fact, this was the first thing we did when we were talking about Moldpot, Andreas and I both chuckled about how, Hey, you know, security is hard, et cetera, and people have open ports on their Mac minis and they don't realize that, but we have access, like we have an entire suite of products just for literally this purpose, right? And that's when, you know, our head sort of cogs started spinning and we were like, Hey, maybe we can use access. Maybe we can set up like, you know, some kind of VPC, et cetera, to connect to other devices at home. We didn't really get to that. But when I show, when we show the demo and sort of set it up live, you'll see what access does for you. And I think there's some real value there because you have a network level block and the ability to do that. So you can't, obviously you can't get rid of malicious skills with that, but what you can do is make sure that only you can reach that URL, you or folks that you, that you, you know, yeah, I see. I think there's some real value to that. The same way that I could go and install a bad app on my phone, right. It's the same sort of that same sort of logic. And then how do you define what that bad app is? It's kind of like this gut of like, Ooh, that doesn't look like something I should be putting on my phone that gives all that access that I want to have. So it's like reminding that. Cause I think you're in that time where you're like, let's go, you know, and you're just like installing stuff. So I think that's a very valid, valid concern there. And by the way, I don't know this specific detail. I suspect the two of you will know this better, or we can look it up. But I feel like Zero Trust, like our suite of products and my apologies for not knowing the details here, because I don't really operate on that part of the org much, but I think it has the ability to even have like allow lists and block lists of domains and that sort of thing. Right. So if you wanted, yeah, exactly. So if you really wanted to set it up and set it up well, you now have a central place to say, cool, like this is on this machine or whatever, this is running somewhere and I have Zero Trust. Like for example, if you didn't ship it on Cloudflare and you deploy it on a Mac mini or whatever, you could still set up Zero Trust on it and at a network level, ensure that that machine can't go to Stripe or can't go to, you know, some domain. So there's some real value there, I think. Yeah. Yeah. Yeah. And it feels like it's kind of ironic, but it feels like we've gone, like it feels like open clause, like a a hundred percent trust versus what should the product should be called, right? The way that you're just like, let's go, like, let it, let it go. So instead of Zero Trust, I, I, I agree. That's, that's cool. That's a cool way to think about it. Let's what, what, all right. So nerd sniped, you're nerd sniped. You start building. What do you reach for? What does this, what does this look like? And actually I I've seen that there's a blog post, so congratulations both on the blog. The blog is incredible. Being able to put, Andres, is that your first blog post or are you already on two? This is my second, actually. The, the replicate announcement was my first one. Awesome. Awesome. So credit, credit to Selso for writing that. Okay. Yeah. Shout out Selso. Yeah. Cause Selso was involved in this too, right? I think Selso's, there's a Selso head on the, on the blog post as well. So there, there is a blog post him. Yeah. He's, he's amazing. He absolutely, absolutely. Yeah, absolutely. So I, there, there, there is a blog post. I want to shout out the blog. Cause the blog goes so deep into technical stuff. So whatever it is that we're talking about here, I'm sure that the blog post has even more. So if like, if we end up nerd sniping, you're here and you're like, I didn't talk about enough of what we wanted. There is a blog post here. So Sid, Sid just posted that out there. So, so we should see that come through here. So but I, again, was at a conference and I didn't get to read this, but I was so excited to read this book. First of all, I love our blog. I think that the world kind of loves our blog. I think when we hire people, there's some sort of, I'm going to make up a stat. It's like 80% of the people are like, oh yeah, I know about y 'all from the blog. It's a great, see Andreas, did you learn about us through, through the Cloudflare blog too? Like Cloudflare originally? No, I don't remember. Oh, okay. But it was, I remember at Replicate, we were always like, let's get on Hacker News with our blogs. And like, how did Cloudflare do it? You know, like every single Cloudflare post ends up on the front page. It's just, I mean, it's great content. I remember reading, it's funny because I didn't know Celso then, obviously, until I joined and like two years in, switched over to his org. I remember reading his blog post on running Doom on workers years ago. I didn't know him. And I remember when I met him, you know, his name seemed familiar and I looked it up. And so I'd seen a lot of the blog posts and it was super exciting because I love how we, you know, now that I'm inside, like I love how we actually really put in engineering details there. Like it's for nerds. I love that. Absolutely. Absolutely. And I appreciate how, how deep we dive. And again, if you want that deep, deep dive, we've got this here, but I'm interested in like, what, what did it feel like? You've got a box of tools. We have awesome primitives, right? So what would you go reach for to start building this thing? I'll let Andreas jump in on that. Well, so, so it was, it was really Brian that built the initial prototype and credit, credit to Brian and, and he built it on sandboxes, which, which are containers. It's runs a Docker image, but, but sandboxes has this nice API for running processes and things like that on those containers. So Brian wrote a script that installs open, OpenClaw as soon as the container starts and, and then wrote like a little bit of, of scaffolding around OpenClaw. It sets up like an R2 sync of, of the sandbox content. So it persists if the sandbox sleeps. It's a nice feature of sandboxes is that they, they sleep when they're not being used with a configurable time to live. So you don't have to pay for it if you're not using it overnight and stuff like that. But it's like, it's, it's, you know, it's a fairly straightforward architecture. It has a worker in front of it. It has sandboxes, access for, for security. And for, for the, for the people at home, the, the R2, you said there is that that's the object storage that we have. Uh, one of the things that I saw recently, which is also cool. And this actually, one of the things that I like about this project is it's really like made this loud, right? That like you can mount an R2 bucket. That's our object storage, like our S3 compatible object storage. You can mount that to a sandbox and then you do whatever, you know, we've been playing around and everybody's been playing around in the, at, like we talked about at the start of this, we've been playing around in these coding agents. And so that stuff's there and it stays. And then of course we're serverless, right? So a serverless sandbox is kind of a concept and you, you touched on it there, but like it, it goes to sleep. So you don't pay for it. Cause you don't want to, you don't want to pay for it the whole time. You don't, you only want this thing running when it's running and you want to wake it up. And when you do wake it up, it's the file systems there at mounts and it goes. So that's, that's a cool pattern. I think that's really cool. That's, that's like, and that's new, that's new-ish to us, right? Like I'd say that's like November-y that we've gotten those superpowers. If not like the mounting thing, it was new to me. I had, I didn't even actually know about it until I saw, saw that happen there. That's really, really powerful. I remember, so one of the things I love working about Cloudflare is that because we're distributed and we have people everywhere, it was really funny because this project was a couple of days, but like we'd go to bed, like Andreas is in Sweden, I'm in London and Brian is somewhere in the U.S. So we'd go to bed and we'd wake up with like 15 more changes. And it was a great way to discover this stuff. I learned about us being able to mount R2 buckets on a sandbox as a part of this. I didn't know that. And it was fascinating because it makes it really easy to be able to like back up on ephemeral compute, like you described, which sandboxes are. Sandboxes are built on top of containers. So you're effectively running a Cloudflare container and you get built only for the CPU time, just like workers. And I think that's the real value there. Cause this stuff can get expensive. It can add up. To add to that, we used a couple of other products at Cloudflare. I think a big part of this exploration was also, Hey, you know, we have all these primitives, I mean, we keep building them and we, at this point, I think developer platform has pretty much everything you really need to build a production app and we have queues. We have workers, workflows, durable objects, access for Zero Trust. Yeah. What did I miss? And, um, the bit that I think was, was really exciting for me was to see how well they fit. Yeah. With each other. We used AI gateway for this as well, which is what I wanted to point out for folks who haven't used AI gateway before. And, you know, they might question what the value that is. I'll give you like a 10 second sales pitch. You know, there's a new model coming on every day, like Craig said, right. And honestly, it's, it's, it's wild. They're all great. And they keep getting better. And switching between them can be a bit of a pain in the butt because you have to like go back, get another provider key and change the URL and like, you know, change sometimes the config, blah, blah, blah. There's no real standard just yet between all these providers. Um, AI gateway kind of fixes that and more. Yeah. Gateway is, um, a sort of lightweight proxy on Cloudflare on the cloud. And you create an AI gateway instance. We have unified billing, which we'll show you in a minute, where you don't have to pay the providers. We'll take care of that for you. Just pay us, set up credits on it. And you can literally use any provider we have. And we have, we have a ton of them. We've got like Replicate, Workers AI, which is our sort of AI platform. We've got OpenAI, Anthropic, Google, and whatever else you'd like. And it just makes switching between these models really easy. Like even while testing, I think we went back and forth between Sonnet and Opus and so on to play with them. You also get observability out of the box. You can actually see what requests are coming in. What's a cache hit. Optimize using that. We use AI gateway. We sort of plugged in AI gateway into MultiWorker for it to sort of be, you know, we don't use Anthropics API. We also played around with browser rendering, which is another product that we have at Cloudflare. Right, right, right. That's the headless browser running. Yeah. That's the one. Yeah. And, and that's cool because, hey, if you're going to run on a sandbox and you want the ability to, you know, use a browser to sort of get screenshots or whatever, like browse the web, that can in fact, that can often be quite expensive to run on the sandbox, right? It's not cheap in terms of compute or memory. Browser rendering is hosted. Everything's taken care of. It's a managed service. You can literally just call an API over a binding and you can browse the web. Yeah. So cool. So cool. Hey, there's a, there's a question that came in across here. Uh, it says, isn't the value of OpenClaw, it's constant heartbeat and checks. The answer to expensive is running the heartbeat with less expensive models, but doesn't, it doesn't have to be 24 seven to, to be going, to be really useful if we think about that, that, that I think it's, I think it's a really good question. And it's something that we're not really taking advantage of sandboxes, um, in the current, uh, malt worker implementation. I like one of the sort of things that we were trying to do with malt worker was like, we, we wanted to run it sort of as it is without changing the internals, but heartbeats sandbox sandboxes are really nice combination. Like if you were to build something like this yourself. Sandboxes has this, uh, you can wake them up on a cron, so you can, you can have them fall asleep and then, and then, you know, at scheduled time, you wake them up. That's not built into malt worker. So, so it's a really good point in that question that, you know, if you want to do a lot of heartbeats, you, you kind of need to keep something running 24 seven. But if I was to build this myself on Cloudflare, it would, you know, it's basically, I've kind of done that since we built malt worker, I just wanted to see what it looked like, just building it straight with Cloudflare primitives. It's not a lot of code, very, very vibe codable. And then you get this kind of, you get the benefits of sandboxes, auto sleeping while you also get the benefits of the heartbeat. So it's all kind of built into the primitive system. It's just that we're not using them for malt worker at the moment. Yeah. And I actually almost somewhat disagree. I don't think the actual value is there. I mean, maybe there is some value there, but I think the real value is having this vented system. Now, if you send a message like via telegram or whatever, and your sandbox is asleep, it will wake up and it will then process that and come back. Right. So you still get the ability to have this evented communication at, you know, you know, even while you're sort of down, we'd spin it up then on demand. Of course, with heartbeats, et cetera, I'd do it differently. Like Andrea said, but yeah. Yeah. I think, and you know, that's, that's a problem that we've solved, right? So Drupal objects has this really great web socket implementation where I can connect to it with a web socket. And as far as my client knows, the server's up and running, but it's not. And when I go to shoot something across there, hello, I'm awake again. I'm, I'm ready to take your message. And it, you know, it's the way that these, the way that our. Our engine runs, right. We're on that V8 isolate engine. So it's like almost lightning fast. You don't, you don't wait for the thing to, okay, here I come. I'm ready. It's like, boom there. So I feel like that's a nice, that's a nice bit. And yeah, I would think that you could do the heartbeat. Like Andreas was saying that you could do the heartbeat with, with cron jobs. I think that you could, could, could, and workers provide cron. Our agents SDK has a nice schedule function as well. So I've seen a lot of people use that to be like, Hey, in 15 minutes, I want you to, or, or, Hey, tomorrow morning, tell me, but what I suggest a new breakfast thing that will just work right. Like in English, drop the, drop a schedule in there. So I think like, I think that if anything, people are going to be nerds night by this and that, that, to that question about this is expensive to run. How do I do this in another way? I think that there's, there are solutions here that, that, that that will be exposed, you know, as, as you go and play with this stuff. So agent, agent SDK has a lot of this stuff already. It's so easy to use that. That's what I was using when I was trying to basically like re-implement open claw on, on Cloudflare. All kind of comes out of the box there. Awesome. Do you, do you have a demo? Do we, we didn't even try to see if you could share your screen. Do you want to try to do that? Or should we just talk through it? Um, we can, we can share and do it. Uh, if you'd like, uh, we have a, I mean, the goal was to, to, to have a really scrappy, um, sort of set up together on the call and, uh, Hey, it could work, it, it may, might not work. I guess, I love it. I love it. Let's do it. All right. All right. So I'll, I'll go ahead and share my screen and, uh, let's see how, you know, how demos go, right? Yeah. This is the first part of the demo. Can he figure out how to share his screen? He did. We're at a hundred percent success right now. That's the demo. Bye guys. All right. So this is the GitHub project for Malt worker. Um, we're calling it Malt worker. We should probably renaming and I don't know what do you call it? Open claw worker. Like, I don't even naming is hard, man. So right. The Malt worker is stuck, but, um, this is the GitHub repository. It's got a huge readme with a lot of things because there's a lot of nuance and a lot of things can go wrong. It's been a pretty active community on issues and PRs already, which is really nice to see. Thank you everybody for that. And what we're going to do is we're going to go ahead and set this up. So I've gone ahead and created a new Cloudflare account called SID account. I don't know why I didn't put the apostrophe S there, but, um, what I'm going to do is I'm going to go ahead and pretty sure it's already cloned. So I have it right here. Let's make sure I have the latest and go ahead and, uh, reset that. And, uh, let's check out Rangda. I don't know what I changed there. So you do have a double screen going on. You see the little, I can see your screen. There's a screen of us, like did the pop out thing. There we go. There you go. Thank you for that. Maybe, maybe the hide the button thing at the bottom there too. That is a really good idea. So you can tell who does this often and who doesn't. Yeah. It would have taken me like 10 minutes to figure that out. All right. So, um, I have the repository, which is great. And this is the repo on Zed. As you can see, it's basically got, you know, this little source file with a bunch of stuff in there, but the most important bit is that we have this, this worker, which is sort of the entry point to everything. Right. And then ends up the sandbox as it's, as it's required. So I won't go too deep into this. I want to go ahead and deploy it for us and see what that looks like now. Hey, deploying things on Cloudflare is actually shockingly easy. If you haven't done it before, all you need to do is NPX Wrangler deploy. I'm pretty sure I don't have dependencies installed. So let me go ahead and do that first. Okay. I am also sure that I would have to edit my NPM RC because I'm pretty sure my NPM RC has some Cloudflare specific stuff. So give me one quick second there. Let's see. Yes. Okay. Now everybody has my secret. No worries. We will, we will cut that in the future. Editor note to the editor. We talked about this before the call about how I'm going to have to rotate basically everything after this call. And I'm prepared to do that. That's okay. So I'm going to go ahead and save that. And now we'll install our dependencies. That should take a quick second. I feel like this should just play like a, like a, some music or something when it happens. Oh, there you go. That was quick. All right, great. So now we have our dependencies and all you really need to do is run NPX Wrangler deploy. It's really that simple. There are a couple of secrets that this needs as you'd expect. We will have to set them up. The good thing is that we can do that after we deploy, because we've sort of built in the ability for it to tell you which ones you're missing, which I really appreciate. Like that was Brian. I mean, Brian's fantastic. So as you can see, this is now building my worker. It's gone ahead and used V to build it because there's, there's a front end bit for the admin that I was describing earlier, it's gone ahead and uploaded everything, which means we should be able to see it in the dashboard really quickly. You'll notice that there's an R2 bucket connected here, which it also created for us, which is multibot bucket, right? And I think Andreas was talking initially about what that's for. Andreas, why don't you tell us more about why we have an R2 bucket here? It's for syncing the, the sandbox file system. I like the, yeah. And what, what is it? It's actually syncing. It's, it's your, well, it's, it's the whole kind of state of open core, like any changes it makes to itself and any paired devices and stuff like that. Yeah. And the, the thing of what's interesting, I mean, what the important part there to know is that open cloud, and by the way, I'd already deployed this. So I have to delete it and deploy it again. Sorry about that. But what's important to know, sorry. Thanks for being honest. Yeah, really show the work. But what, what you have to remember is that open core will write a lot of stuff to disk as you work with it, right? It has memories and skills and all of it. That's how it stores stuff, right? Like, I feel like that's, that, that's kind of like, that's its database, if you will. Absolutely. As you know, LLMs are great with Markdown. They tend to use that the very sort of Markdown native, right? So they'll store all of that stuff on disk. But when you have these ephemeral containers, you might not have a disk. And that's what, that's what we use R2 for, like Andrea said, we use it to sync that so that even if it isn't alive and then like wakes up later, it still has all the stuff that it would have expected. Nice. So I now have this deployed in theory, right? So I've gone ahead and deployed it. You'll notice that it also deployed a sandbox. It said the image already existed. In fact, that's why I deployed it earlier. Cause you know, no one wants to watch my machine build a Docker image for five minutes. So now that this is up, I should be able to just hit this URL and see what it says. There you go. Now it said it can't run because there's about 15 secrets that haven't added yet. And, and, and, you know, that can be really tricky for people to sort of know which ones they miss. I'm really, you know, I'm really proud of the screen that we have here. So we're going to go ahead and add each of these secrets one by one. I'm going to go ahead and open workers and pages on the dashboard. This is the Moltpot sandbox worker that we just deployed. And I'm going to go ahead and add a bunch of these secrets one by one. So let's go through them together. We have the Moltpot gateway token. Now this is purely a sort of shared secret between the browser session. So it's not, you know, it doesn't have, I mean, it's, it's something that you can just generate yourself and go ahead and paste there. I think we generated one with open SSL a little while ago. So I've gone ahead and pasted that here. That's what that is. Next you're going to need, let's see, CF access team domain. This is a fun one. So you want to set up Cloudflare access, like, you know, we were talking about earlier. Cause in theory, you want to be able to be the only one who accesses your bot. It would kind of suck if anyone else logged in and was able to, you know, use your things. So what you want to do for that is set up the Zero Trust. Ooh, what did you do right there? How'd you do that? Command K. Command K. Look at that. That's really nice. I love it. There you go. So zero trust access controls applications is what you want to open. Now, like we, you know, said previously, Zero Trust is this way to have, you know, these, this sort of often, often a Nazi sort of proxy in front of your app and Cloudflare, and I think it's really sort of underrated. I think it's, it's an absolute banger. So I'm going to say, yeah, you're like, oh wait, we have all this. Yeah. Every time you need to do something like this, you're like, wait, I can do this. It's wild, isn't it? We use this a lot internally, right? We put a say, anybody who's, you know, if you're building an internal app, if you're like, Hey, I'm going to, I want only people with this domain to be able to access here, it will actually send you an email link and all that stuff. It's really handy. So this is called access. Fantastic. It just, yeah, sorry. One thing I've been doing with access is I've checked out the Cloudflare Terraform repo to my local machine. And then I've asked Claude to write me Terraform for, you know, any kind of access rules he wants, know it, can sort of read through all of the documentation in the Cloudflare Terraform repo. And like in 10 minutes you have like a, you know, a secure login screen for your thing, which would have taken, you know, a couple of hours of work before. Super clever. That's really clever. I like that. I love that we support Terraform across the board for a lot of these things. So like, if you're not like, you know, silly like me, who uses the dashboard to set everything else up, that can be a really quick way to sort of, you know, get more done by just like setting. And also often you want your infrastructure to be sort of Terraformed, isn't it? Yeah. Yeah. So I've gone ahead and created this access application, as you might've seen. There's also a policy that I've created. You have to sort of create multiple policies based on sort of who can use it. Right. And all I've said is that only include my email. And please don't send me spam on this. I just got it. But so that's what the policy is. It would make sure that only I can log in and only people who have access to this email address can log in. Right. I've gone ahead and deployed the application to one subdomain, which is the one we just deployed on, which is, you know, where the worker is. Sandbox dot, you know, blah, blah, blah. And the, the, the keys that I was initially setting up, one of them needed my application audience tags. I'm going to go ahead and copy that here. And I'm going to create a new secret based on the value. I do not remember what I believe it was. This one, wasn't it? It's confirmed that yes, the CF access audience. So that's the second one. This is going to be a long evening folks. There's this CF access team domain. Now this one's interesting because you can obviously create, you know, you can have multiple access policies across organizations and teams. You want to pick the right one. And the way to find that one for my account is you go down to settings and you copy it from here. All right. So we're going to set that one up. That's done. All right. We have a few more. I'm realizing, I'm realizing right now that you must run into places where they use, you know, a lot of services use SID for like service ID or string ID. That must be really confusing for you. It's like, right. Yeah. Yeah. You're not wrong. So you need an account ID so that we know, or rather, you know, the app knows which account ID to make API requests to for Cloudflare. I'm going to go ahead and give it this account ID as a value. And I know this is boring, but give me another minute. I'm having a great time, Seth. Don't I appreciate it. You're doing great. You're doing a great job talking through what this is and that this is all set up. And then Andreas already mogged you and he's like, I would have just done this with Terraform. So you already got mocked. That's what, that wasn't my intention. I think it's just, I think it's just a neat, neat, like, like the things you can do in 2026, you know, just like writing Terraform used to be this like hellish, you know, figuring out this DSL and stuff. And now you just point a claw at it and it just does it. It's amazing. Dude, I've been in Terraform by hand years ago and I'd never enjoyed it. And now with MLMs, it's, it's the things that you don't enjoy doing, which you don't have to do anymore now as a result. It's wild, isn't it? That is exactly when you should reach for AI. Every time you're like, I don't want to do this. I don't need to. Yeah. Oh, CSS. Oh my gosh. It's in Terraform. Yeah. I'm going to create an API token. Now I have $10 on this account. Please don't steal my token. But if you do, you know what? Enjoy. Yeah. Yeah. You deserve it. If you get it, you deserve it. If you figure this out and copy it with that one frame, then good for you. Use the $10. I support you. All right. So we have these secrets up now, right? So to recap, I added a Moltpot gateway token, which is to be able to sort of authenticate my browser with Moltpot. There's a CF access audience, which is the audience. Like it's just a tag for the specific app that, you know, that was set up on access that we set up right now. The team domain, which is specific to my account. Gateways account ID, because we're going to use AI gateway. So I just copied my account ID. The gateway ID, which is, you know, I created an AI gateway and I added the $10 to it, the name of it, you want to pop in here and finally an AI gateway API key. And that's it. I'm going to hit deploy now. Let's see what happens. All right. Fingers crossed. And that AI gateway name, you might say like for what team it's for or something more specific than just AI gateway. Yeah. Don't name it. Don't do it. Don't name it. It's like naming a worker called worker. Don't do that. Don't do that. The old X variable. Oh, I'm going to hit refresh now. And this time it should, there you go. All right. Waiting for more to occur to load. Now, by the way, you would have seen access typically. You don't, I didn't see it here because access is really smart and sort of makes sure that you have, you know, it's, you know, my browser has a cookie and it knows how to identify me and it keeps the session open for 24 hours. If I hadn't already logged in previously. And if you, if one of you folks want to hit this URL you might want to open it in an incognito window, just so we see what it looks like. That's not a bad idea. I was thinking that will also, oh, there you go. That worked. Funnily enough, sometimes this also just works because I have zero trust on my machine and like, what was really cool. Cause it has this ability to like keep you logged in even on different browsers, which I find really fascinating. But yeah. Customers of workers and the Zero Trust framework love the fact that they can do that, right? Like anybody who's on, on our, that's what this is for. Anybody here could just log in. So yeah, absolutely. And as you've noticed now, I entered my email address. And if I'd entered an email address that wasn't in that policy, it wouldn't work. But because it is, if I enter the code right now to log in, you'll notice that I'll be in, so this is, this is how you sort of protect your, you know, any site really, not just OpenClaw, but this is how you use access. Um, all right, I'm gonna close the incognito window, go back to this one. You'll notice that it says pairing required. Now this is an OpenClaw thing, which, uh, by the way, this is the OpenClaw dashboard, if you didn't notice. But, um, you have to pair every sort of session manually. I think OpenClaw typically wants you to do this via the CLI. Okay. We don't really have bash access to that sandbox. What we've done on our Malt worker is built this admin thing that shows you the pairing requests. And when I hit approve now, you know, which is on my Mac Intel, which actually is a lie, it's not Mac Intel, it's Mac, Apple Silicon, but whatever. When I hit approve, it is going to call the CLI under the hood in the sandbox to sort of approve my pairing request. That makes sense. So let's give that a second. This can take some time. I've noticed. We've got, you've got a little, your window came back, the window that you so carefully closed this back. You opened an incognito window. It was, that did it. All right. So now you'll notice that I'm in, okay. Which is shocking because I did not expect this demo to work. Well done. Hey, all right. Let's see. Let's see. If nobody else, that's true. That's true. Let's not get ahead of ourselves. Okay. I don't know guys. It says health. So this is the open cloud dashboard and I'm going to go ahead and say hello there. And in theory, it should respond by using AI gateway to call, I believe Opus or Sonnet is the default. I forget which one Andreas will know. Yeah. There you go. Hey, I just came online. How sweet is that? So they all, they have like a nice, there's a nice system message vibe to this thing. Yeah. Okay. You know what? Here's the, you know, you were talking about R2 and you were talking about this stuff, by the way, I haven't set up R2 on this one. I don't think I have, maybe I did. I don't know. We should check, but I can give it a name. I'll call you agent Smith. Careful. Yeah, I know. Right. Yeah. What am I manifesting? Yeah, you did this. And this is how it began. Tricks. It got it. It got it. Yeah. Now that we have this, I know we don't have a lot of time, but I want to show you one more thing. Okay. Just one more thing. One more thing. I'm going to set up Telegram on this, right? Now I've spun up a new Telegram. And, you know, if you haven't used Telegram before you have this, they have this bot called bot father when, where you can sort of tell it to like create a new bot. So I'm going to say that, and I'm going to say, I'm going to call it agent Smith. And let's choose a username. All right. Let's call it agent Smith and oh, it's invalid. Someone's already using agent Smith. So I'm going to call it agent Smith one. Wow. That's also gone. Okay. Wild. Okay. I'm going to do Zolder, aren't I? Yeah. It has to end with bot. All right. Sid's agent one. Okay. That also doesn't work. Oh, I'm in bot. Sid agent bot. There you go. It only took 18 attempts, but now, and I can, this is where things get interesting. I can just give this token to Claude and have it set it up itself. So I'm going to say, Hey, I want you to be able to text me on Telegram. I've can't type when people are watching. I've created a bot. Shall I give you the token? I don't try this at home kids, but yeah, there you go. It says, yes, that would be great. Give me the token. I'll get it configured. You know, you remember Andrea saying how it'll just set things up for you. This is, this is, this is that, right? So I'm going to send the token. Let's see what happens. All right. Perfect. Let me get that configured. All right. So it's generating a skill. Am I, am I right? What, what is it doing? We don't know. We're just, it's running. It's not a skill in this case. Cause I think what Peter did, which is really smart, is that a lot of stuff is just built in. So I think Telegram, as far as I understand, it's just like built in. You don't have to configure it or add anything. I mean, you do have to configure it with a secret after you create a bot, but you don't have to install anything or like set up anything. Gotcha. Um, now I don't know if it's actually done. I'm going to ask it again. Cause I'm impatient. Is it now set up? Did it send you a message? Nevermind. It was already looking at it. It was queued. It says it seems Telegram is implemented as a plugin. So that's what I was talking about. Oh, okay. Cool. Plugins. He's already created these plugins. Yeah. Gotcha. Okay. And by the way, they have a lot of them. Like if you go to their website. Yeah. And it's open. It's, it's open. So yeah, you can, you can add your, your plugins there. Okay. That's cool. Absolutely. And then. I saw a thing. I know we're coming up right on time here and I know you guys probably have other things, but I saw like people, they made a social network. Yeah. And there's like mult book and the agents were hanging out and it felt like straight out of science fiction, right? Like, and they share who they are. Cause you just created that dude's name. You just called that guy, agent Smith. And that agent Smith can go and hang out in a social network. That's made for agents. Is that yeah. It's mult book, isn't it? Mult book, right? And then I saw, I saw that some of these were having problems doing actual tools. Like it's like just physical shit. You are sorry. Sorry. Sorry. Stream physical stuff that you can't do. Like, and they made a website called rental human. Have you seen that? Rental human.ai. Yeah. And it's like, it's like go in house and flip switch. Right. So it's like anything that's not, it can't control rental human .ai. That is just wild to like. At some point they were trying to invent a new language to speak because they know that humans are, are, are watching. Yeah. That's why I think that that's people. Is it, is it the agent itself doing it or is it people, or is it like, cause science fiction's in the training set? Like what's going on? It's people, it's people kind of prompting their, their books to go and say stuff on, I think, I think mult book kind of, um, it got taken over by a selling crypto or whatever. Yeah. Yeah. So yeah. By the way, this was done. In fact, I made it do the pairing itself. Cause I didn't want to have to deal with like, you know, like I said, the CLI. We didn't even add the ability to actually pair, like approve the pairing request on the admin, but I just said, Hey, OpenClaw, can you, can you like, I'll give you, just go ahead and do it. Yeah. Just do it for me. Now for the sort of the final bit of this little demo is what's up Smith. Let's see if it responds or it's typing. Apparently. Fascinating. All right. So Telegram has a bot and it's passing it over to your. Oh, I see it over there. Oh my gosh. Hey, the Telegram bot is working perfectly. We just got all of this. Well, so, uh, it was that easy. It really took us what? About maybe 15 minutes to set this whole thing up. And hey, most people are faster than me. I'm, I'm getting old. No one needs the song. And Andreas is just going to terraform it. So like. And this would be done like yesterday. Honestly, I don't, we should have let him. No, you're, you're, you're, you're fast. I mean, it's fun watching you with the. And I like, I want to like, just, just shout out to get nerd sniped in the today's times. Right. So I'm sure like y'all played in that space and you were probably didn't write all the code or didn't, didn't, but putting those pieces together and using AI to build AI, I think it's like awesome. So, and thank you for sharing it. You know, like, I think that like shout out to all the blog, blog authors out there on the, on the Cloudflare blog that, that do do this and do post about this stuff and then share the code. Right. So for, for inspiration. And again, this is not, do not go run this. This is, this is a, this is a proof of concept and we want you to take this and fork it and make it cooler and find the places and, you know, people are raising valid concerns there. Let's help fix that. Let's figure out what those are. Like if, if we want to come up with like, how do we know that this is a bad skill or not malicious, right? Like, how do we do that? It's all on us, right? This is open. This is open. And thank you for pushing this open as well. Uh, y'all, I think that this is a nice way to, I don't need to go buy a Mac book mini. It turns out, sorry, Apple. That was probably really awesome. Probably we should have all bought stock, uh, during that time period. So that was cool. Oh, it was a good week. Wasn't it? It was a good week. But thank you all for jumping on here and sharing your wisdom. I hope to do more of these and, uh, see you all around more and everybody. Uh, we'll get a recording of this up. So I saw a couple of people were like, Oh man, I'm late to, I missed the first part of this. We'll make a nice recording of this. We'll get it up on the YouTube channel. Follow us there. Follow us on Twitter. Uh, where should we follow y'all? Uh, why don't, why don't you just, uh, uh, say, how do we, how do we connect? How do we follow you in the future, Sid and Andreas? So I'm, um, chat Siddhartha on Twitter. I'm going to post it on, most people can't spell it. So I'll post it on chat and that's me. And then Andreas, is that something you, oh, there we go. And Andreas posted his too. I've also posted a link to the GitHub. That's where, that's what you want to fork or clone. If you want to run it again, proof of concept, technical showcase at your own risk. Be careful. It's fun. You know, try it, play with it and then make it better. Awesome. Awesome. Thank you both for making it better, for bringing that forward and letting everybody play. That was super cool. I, that was the demo that I needed to understand what is upon us right now. So cool. I can't wait to go play with it. Thanks for setting that up. I'm, I'm all ready. I'm ready to go play with that thing. All right, everybody. Thanks. Great. Bye. See ya. See you soon, everybody. Thanks. All right.