The OpenClaw Guide no PM is Talking About (Masterclass for AI PMs)

SPEAKER_00

It's up to 245,000 GitHub stars. There's over 2 million weekly visitors. OpenClaw is going totally viral.

SPEAKER_01

Today, we're going to break that down. How to set it up the right way. Security stuff that seems benign, but you really can't skip.

SPEAKER_00

The question on everybody's minds is how do PMs actually use this tool?

SPEAKER_01

Versus a traditional LLM, which is more reactive. Here, you can really take the reins of whatever you're trying to do and be proactive. Here, you can set it up to execute even when it's 3 a.m. and you're asleep. You're not even at your computer.

SPEAKER_00

I know one of the toughest parts is actually setting it up. I've tried to teach a couple people this and this is the part that once they do it, they're unlocked. So can you walk us through the easiest no stress setup guide you could find on YouTube?

SPEAKER_01

There is a simple three-step process that you can just use on your terminal. If you're not seeing red, you're good.

SPEAKER_00

Should you be using a VPS or Mac mini, Telegram or Discord? What about the security risks everyone keeps talking about? We will answer all your hottest questions.

SPEAKER_01

We are going to turn any Slack channel into an AI-powered knowledge base that answers team questions from your product documentation. Every morning at 9 a.m., OpenClaw scans your team's Slack channels. It summarizes what happened overnight, identifies blockers, and posts a concise stand-up brief to product stand-up that replaces the 15-minute context-gathering ritual. [SPEAKER_00] So product managers are getting one step closer to Iron Man. [SPEAKER_00] Before we go any further, do me a favor and check that you are subscribed on YouTube and following on Apple and Spotify podcasts.

SPEAKER_00

And if you want to get access to amazing AI tools, check out my bundle, where if you become an annual subscriber to my newsletter, you get a full year free of the paid plans of Mobbin, Arise, RelayApp, Dovetail, Linear, Magic Patterns, Deep Sky, Reforge Build, Descript, and Speechify.

SPEAKER_00

So be sure to check that out at bundle.akashg.com. And now into today's episode. Naman, welcome to the podcast. [SPEAKER_01] Thank you for having me. So we've all seen the hype. It's up to 245,000 GitHub stars. There's tons of forks. There's over 2 million weekly visitors.

SPEAKER_00

OpenClaw is going totally viral. And it's had a tumultuous history. It used to be called ClawedBot. Anthropic asked him to change the name. He changed it to Mopah. He realized that it wasn't such a good name. He called Sam Altman. And Sam said you can call it OpenClaw. It was called OpenClaw. And then a week later, Sam bought him for over a billion dollars. And the question on everybody's minds is how do PMs actually use this tool? So why should PMs actually care about OpenClaw, Naman?

SPEAKER_00

[SPEAKER_01] Well, so the biggest reason would be that versus a traditional LLM, which is more reactive, here you can really take the reins of whatever you're trying to do and be proactive and plan ahead in terms of whatever you're willing to accomplish. [SPEAKER_01] What that looks like in practice is that instead of conversationally asking it to do things or asking it questions, here you can set it up to execute even when it's 3 a.m. and you're asleep. [SPEAKER_01] You're not even at your computer.

SPEAKER_00

[SPEAKER_01] Finally, the biggest benefit in terms of usage itself is that it's not cloud locked, which means that you can plug and play whichever LLM you want based on the use. [SPEAKER_01] If you're doing more deep research type work, you can plug in Opus versus if you want a faster response to a customer, maybe you can just use the fast Gemini model. So I've been playing with OpenClaw for weeks now, and I know one of the toughest parts is actually setting it up.

SPEAKER_01

[SPEAKER_00] I've tried to teach a couple people this, and this is the part that once they do it, they're unlocked. [SPEAKER_00] So can you walk us through the easiest no stress setup guide you could find on YouTube? Yes. So when it comes to setting it up, there are two broad ways to do this. And I say broad because the only thing in common they have is the first step. After that, they look completely different. The first of those two will only take me 15 seconds to demo. It's actually crazy how easy it is. But really all you have to do. So for the first easy, almost training wheels setup, all you have to do is go on emergent.sh.

SPEAKER_01

Some of you might be familiar with emergent.

SPEAKER_00

[SPEAKER_01] It's a competitor to lovable, give or take. [SPEAKER_01] And what they've done here is they've put in this moldboard feature right here. [SPEAKER_01] So what this lets you do is literally one click your installation. [SPEAKER_01] It just pastes everything you have to run here.

SPEAKER_01

The only thing you replace is your LLM key itself, which just goes in there. You do that, hit this little enter button. It just sets it up for you. The reason why we will not focus on this approach is that, as you can probably guess, it is restrictive in nature. It does not allow you the full freedom to run OpenClaw on your computer machine, use your RAM, run your LLM locally. So, but in case somebody is looking for a really quick and easy out of the box type setup, that is available simply by going on here. Cool. So now close that. Before we start actually pasting commands, remember that anytime you get stuck here, this stuff can be intimidating.

SPEAKER_01

But really, if you just reverse Google whatever error you're getting, it's very easy to figure out. We might run into a few here. We'll see. But the first command you want to paste is quite simply called npm install hyphen G. OpenClaw at latest. What this does is it finds out the latest version that's available. You hit enter. I'm hoping this gets us some errors so I can live troubleshoot them. But looks like it's going fine for now. We'll see. [SPEAKER_00] You might not have npm or something like that installed and you might need to install that. [SPEAKER_00] So that's node package manager versus from node.js. Out. We might run into a few here. We'll see.

SPEAKER_01

But the first command you want to paste is quite simply called npm install hyphen G. OpenClaw at latest. What this does is it finds out the latest version that's available. You hit enter. I'm hoping this gets us some errors so I can live troubleshoot them. But looks like it's going fine for now. We'll see. [SPEAKER_00] You might not have npm or something installed and you might need to install that. [SPEAKER_00] So that's node package manager from node.js. [SPEAKER_00] And you'll run into these issues when you're using terminal. [SPEAKER_00] The most important thing to do is persevere.

SPEAKER_01

[SPEAKER_00] Just Google or take a screenshot of your screen and drop it into ChatGPT and they will help you. Perfect. Perfect. So that looked like it worked.

SPEAKER_00

[SPEAKER_01] So my quick and easy way to figure this out is if you're not seeing red, you're good. [SPEAKER_01] Sometimes you'll get a bunch of warnings, but they're fine and acceptable. [SPEAKER_01] So as long as you're not seeing bright red and error, you're probably fine. [SPEAKER_01] The second command is the open claw onboard. [SPEAKER_01] Before I run this, I want to walk through what happens when you actually do this. [SPEAKER_01] So just for context, Peter Steinberger, who invented this, the origin of the problem he was trying to solve was to have a bot that he could WhatsApp.

SPEAKER_01

So it started there in his head. But then he was thinking, why stop there? He wanted this bot to have a complete personality of its own. And I know you can give personality to your Claude or whatever, but he really wanted to bake this into the entire soul of what he was creating here, which is why I think you'll find it interesting that there's actually a soul.md file that gets generated that you can impart whatever you want in terms of attributes to. And then the way it is configured is that you cannot skip all that stuff. It'll force you to give it a name, tell it how you want it to interact, tell it how you want it to interact with you and so on and so forth. Right.

SPEAKER_01

So this is very interesting. We'll hit enter here and see what it throws at us. Okay, great. So now we're officially in, right? So there's obviously a big security warning. I don't think anyone has read this, not even Peter Steinberger, if I were to guess. You just say yes here. This is just saying that it requires lockdown in terms of your environment. It's not really that scary. You just hit left arrow, hit enter. That's the thing, guys. [SPEAKER_00] Your mouse isn't going to work here. [SPEAKER_00] Don't get scared. [SPEAKER_00] You can either use the arrow keys on your keyboard or you can actually use tab too. [SPEAKER_00] And then you just hit enter. Great call out.

SPEAKER_01

So here you can go down the manual route, but the reason I would not recommend that is the quick start is actually comprehensive enough for the manual to start feeling way too much work, especially when you're trying to set it up. Also know that even if you skip steps here, it's very easy to set them up later. So it's actually not a big deal at all. If you pretty much just speed run through this entire thing and go from there. So next up, as we were talking about, because we said that this is agnostic of model, these are literally all of your options. I'm sure there's probably more, and even if there's something not mentioned here, there is a way to run this.

SPEAKER_01

What I would like to do is use Google because lately, I've just been a Gemini API kind of guy. Just a random side note. I do feel in terms of dollar value, it gets me the farthest while still not compromising on quality that much.

SPEAKER_00

[SPEAKER_01] That's just my reasoning. I'm sure it depends on what you do. [SPEAKER_01] So I'll pick Google and then I'm going to, I already have my API key. [SPEAKER_01] If you want to create one and don't have it already. Today's episode is brought to you by Jira Product Discovery.

SPEAKER_01

[SPEAKER_00] If you're like most product managers, you're probably in Jira, tracking tickets and managing the backlog. [SPEAKER_00] But what about everything that happens before delivery? [SPEAKER_00] Jira Product Discovery helps you move your discovery, prioritization, and even roadmapping work out of spreadsheets and into a purpose-built tool designed for product teams. [SPEAKER_00] Capture insights, prioritize what matters, and create roadmaps you can easily tailor for any audience. [SPEAKER_00] And because it's built to work with Jira, everything stays connected from idea to delivery. [SPEAKER_00] Used by product teams at Canva, Deliveroo, and The Economist.

SPEAKER_01

[SPEAKER_00] Check out why and try it for free today at Atlassian.com slash product dash discovery. [SPEAKER_00] That's A-T-L-A-S-S-I-A-N dot com slash product dash discovery. [SPEAKER_00] Jira Product Discovery. [SPEAKER_00] Build the right thing. [SPEAKER_00] Today's episode is brought to you by Vanta. [SPEAKER_00] As a founder, you're moving fast toward product market fit, your next round, or your first big enterprise deal. [SPEAKER_00] But with AI accelerating how quickly startups build and ship, security expectations are higher earlier than ever. [SPEAKER_00] Getting security and compliance right can unlock growth or stall it if you wait too long.

SPEAKER_01

[SPEAKER_00] With deep integrations and automated workflows built for fast-moving teams, Vanta gets you audit-ready fast and keeps you secure with continuous monitoring as your models, infra, and customers evolve. [SPEAKER_00] Fast-growing startups like Langchain, Writer, and Cursor trusted Vanta to build a scalable foundation from the start. [SPEAKER_00] So go to Vanta.com slash Akash. [SPEAKER_00] That's V-A-N-T-A dot com slash A-K-A-S-H to save $1,000 and join over 10,000 ambitious companies already scaling with Vanta. Perfect. Yeah.

SPEAKER_00

[SPEAKER_01] So you just go on, you literally just Google "Google Gemini key create," it'll bring you to this site that I've been on many times. [SPEAKER_01] I, wait, is it that one? [SPEAKER_01] Yep. [SPEAKER_01] So create a new Gemini API key. [SPEAKER_01] Actually, there's no blurring either. [SPEAKER_01] We will be fine. [SPEAKER_01] But really, you just click this create API key. [SPEAKER_01] You give it a name. [SPEAKER_01] You might want to call it open claw. [SPEAKER_01] And then I'm not going to do it. [SPEAKER_01] Perfect. [SPEAKER_01] Yeah.

SPEAKER_00

[SPEAKER_01] So you just go on, you literally just Google "Google Gemini key create," it'll bring you to this site that I've been on many, many times. [SPEAKER_01] I, wait, is it that one? [SPEAKER_01] Yep. [SPEAKER_01] So create a new Gemini API key. [SPEAKER_01] Actually, there's no blurring, either. [SPEAKER_01] We will be fine. [SPEAKER_01] But really, you just click this create API key. [SPEAKER_01] You give it a name. [SPEAKER_01] You might want to call it OpenClaw. [SPEAKER_01] And then I'm not going to do it. [SPEAKER_01] But when you create a key, it'll just generate the key.

SPEAKER_00

[SPEAKER_01] Make sure you copy it and put it somewhere safe because sometimes it doesn't let you reaccess it once you've created it. [SPEAKER_01] So really straightforward. [SPEAKER_01] I won't be doing this again because I already have a key stored separately that I'll just be using over here. [SPEAKER_01] So I'm just going to hit enter here. [SPEAKER_01] I'm going to use paste API key now.

SPEAKER_01

So, okay, great. So you can just paste your key. Just try to not broadcast it over the internet. And then you hit enter. So then next up, this is also what I was mentioning. It lets you choose exactly which model within Google to use. You can just go with the biggest, brightest one, which right now as of recording is Gemini 3 Pro. However, as I was mentioning, if this is going to be a Slack bot that end customers are going to be interacting with, they probably don't need to wait 10 to 15 seconds for each response. In that case, if you just pick any of the Flashes, those are known to be really quick. So it just depends on your use case, right?

SPEAKER_01

For now, we'll just use the default, which is 3 Pro. Hit enter on that. So the other really cool thing about OpenClaw is that it really has one gateway that then connects to all of the rest of the internet. So what this means is if you're running it on your WhatsApp versus also on your Slack, maybe you also have a Discord going for some reason, you don't need to create different gateways for that. All of it sits under one place, neatly organized. And you can then also use that one gateway to monitor and even delete any of your operations that you have going. I'll also be sharing how you can see the UI version of that in case the terminal scares you.

SPEAKER_01

But what this is asking in terms of our setup is what we want to set up first. Again, you can add on to these incrementally. You do not need to create a new gateway. It's really straightforward. Now, because this is catered towards product managers, obviously, I know you all love to live and breathe on Slack. So we'll just be choosing Slack socket mode. Some of you might be familiar with what socket mode is, but don't worry if you're not, because we'll be going through the entire setup on Slack end to end for you all. So great. We can just use, you can just have this be OpenClaw. Great.

SPEAKER_01

So the way this works is when I was setting this up before, these instructions are pretty bare bones. So what I did was I compiled actually easily followable instructions because the terminal instructions aren't the greatest. What I did was compile all of these instructions for you. If you're wondering where these came from, there's actually a TUI of OpenClaw itself where you can ask questions about what you wanted to do. So say you're stuck at any given stability, anything you're trying to do, you can actually ask OpenClaw to help you figure it out. Right. So that's just what my source was for getting this.

SPEAKER_01

So we're going to be toggling back and forth between what it wants and how to get it. So as you can see here, the first thing it would like is the Slack bot token. And it always begins with an XOXB. We see here the steps that we need to follow. So we're just going to be doing that step by step. Great. So just for this demo, I actually set up a brand new Slack for you guys, just so we would be able to go through this together. Because as Akash was saying, there's a decent amount of pitfalls here to dissuade even the most persistent of you all. So we'll just go back here. As you can see, step one is go to api.slack.com/apps. So we'll just go there. Great.

SPEAKER_01

So this is what you want to do. Create an app. Again, for the PMs out there, I'm sure you know what I'm doing. This is all very familiar for you all. Next up, this explains literally everything, right? So it says choose from scratch and name it OpenClaw. So we'll say from scratch, we'll say OpenClaw here. And then I'm just going to pick the one workspace that I have. So this is straightforward enough. We'll do create app. So this is where the magic begins. Next up, you want to select, click socket mode on the left sidebar. Socket mode. This is really straightforward. You literally just have to follow these steps. As you can see, enable socket mode. You just click that.

SPEAKER_01

Anytime you're confused, just go back here. Toggle on. A box will pop up asking for a token name. Call it secret token. Great. No need to overthink this. Secret hyphen token. Hit generate. Perfect. So it generated what looks like is something we need. It starts with xapp. So we're just going to copy it and keep it somewhere safe for now. We'll be needing it in just a minute. So this part is done. As you can see though, in our terminal setup, it wanted the Slack bot token. So what we just did was a stepping stone to where we're trying to get. But we need that as well. I think it lists this after that. No need to overthink this. Secret hyphen token. Hit generate. Perfect.

SPEAKER_01

So it generated what looks like something we need. It starts with xapp. So we're just going to copy it and keep it somewhere safe for now. We'll be needing it in just a minute. So this part is done. As you can see though, in our terminal setup, it wanted the slack bot token. So what we just did was a stepping stone to where we're trying to get. But we need that as well. I think it lasts after that. But we'll just continue down our process. So we did this. We did this done part. Now we'll go back. Left sidebar. OAuth and permissions. I lost my little window here. Great. OAuth and permissions is right here. Scroll down to scopes. Bot token scopes.

SPEAKER_01

So yes, this is right here. So we'll be adding all of the scopes that we want our bot to perform. What this translates into is we're going to be giving it permissions to read certain channels, respond to certain channels, make sure that it has all of the background knowledge, really, that it needs from all over the workspace to do its job really well. So as you can see, this goes over exactly all of the permissions that we need. So I'm just going to make this slightly thinner so we can see. So all we want to do here is, as it says, bot token scopes. Make sure you don't do user token because that's something different. We don't want to do that.

SPEAKER_01

We just want to add all of these scopes. So you click that. First up, it says chat, right? When you start typing chat, it just shows up. You click that. Then you go on to the next. So I am read. You keep going until you do all of these things. Obviously, feel free to skip any of these that you wouldn't want. It does explain what each of these things do. I would say all of these are important. But if you have an organization that has rules against these, by all means, feel free to skip. Channels, history is right. That. And then finally, groups, history. [SPEAKER_00] That's a good one. [SPEAKER_00] I am right. Great catch.

SPEAKER_01

And actually, that is the most important one because we would not be getting any messages otherwise. Great. So that ends our screenshot here. But this is our final one. So we'll bring back our application. I'll just go full screen here. So once you save these, there won't be an option to save. What you want to do is go all the way up and you'll see this install to workspace option that you did not have before. So you just click that. It'll ask you for these permissions. You hit allow. Great. So now if you see this, this should now look familiar because this is exactly what we want to paste into our terminal.

SPEAKER_01

There are still a few more steps, but I'm curious to see at which point we will be prompted. That's not what I wanted to do for them. But for now, we'll go back to our terminal. Paste our token. Hit enter. Great. So remember how I said the first, the stepping stone, so to speak. This is where we'll grab that. Thankfully, we already expected this and we have saved this. So we'll just throw that here.

SPEAKER_00

[SPEAKER_01] Hit enter. [SPEAKER_01] So, yes, we do want to configure channels access.

SPEAKER_01

I have the liberty to just allow all channels. Again, if you have restrictions, feel free to act accordingly. Great. So if you see here, this is actually important. So these directories that it's updating, remember that these don't live on the cloud somewhere. These are all on your computer. These are all local files that are saved on your machine. And as I was mentioning before, if you think this is too much work to just go through the terminal and do this, you can do one of two things. First, you can simply ask CloudBot, or I should say open Cloud, to do all those things for you.

SPEAKER_01

Second, you can go into your finder, go to the file path, open the file using sublime text or whatever you have, and do whatever changes you want it to do manually. So those two are your options. We would. So essentially what this is saying is that our Slack configuration is complete. When it says configure skills now, what it's talking about is unrelated to Slack. This pertains to one of the things that we were talking about before, which is a capability that OpenClaw has. So the two really important things that you want to set up, you can choose whether you want to do it during installation or later, are skills and tools.

SPEAKER_01

So the way Peter Steinberger, literally the inventor of this thing that we're demoing, chose to describe each of them was, and I quote, tools are organs. Can the agent do it versus skills are textbooks. Does the agent know how to do it? I feel like that really, for me, really put into perspective what these things are. Again, as I said, if I just hit yes to show you what goes on here, these are all of the skills that are, so these are all open source. These are just people and good-hearted developers of the world. They just developed these. Once Peter Steinberger already made his project live on GitHub. So a lot of these are constantly evolving.

SPEAKER_01

I remember seeing one for Philips Home. Let that sink in for a second. You can WhatsApp something to a bot and it changes the light in the room that you're sitting in at 4 a.m. to wake you up. I don't know. That just breaks my brain to think that's a possibility. As I said, we'll just skip for now. The way to select it is by hitting space. And then if you hit enter, it'll just skip. Again, the reason why we skipped. [SPEAKER_00] Yes. [SPEAKER_00] If you build it, space, it won't select it. [SPEAKER_00] If you just hit enter, you'll hit this annoying issue. [SPEAKER_00] So just space, then enter. [SPEAKER_00] Exactly.

SPEAKER_01

I don't know. That just breaks my brain to think that's a possibility. Like I said, we'll just skip for now. The way to select it is by hitting space. And then if you hit enter, it'll just skip. Again, the reason why we skipped. [SPEAKER_00] Yep. If you build it, space, it won't select it. If you just hit enter, you'll hit this annoying issue. So just space, then enter. Exactly.

SPEAKER_01

Yep. And then, as I was saying, you're not really missing out because we will be going over how you can add hundreds of skills if you want. I just found it easiest to modify the text file. You can even use an LLM to generate a really long, verbose, super comprehensive skill and then paste that in versus having to do it this way. So this is just my preference. I think most people would agree. I don't think we need to set up go places just yet. So we'll hit no there. We're not generating images for now. So we might as well just hit no. But I think because you're using Google, one of the benefits is you can use your same API for pretty much everything. Vertex API allows you to use the same key for text generation, image generation. Even if you're trying to do video generation using VO, you can use that. Again, it makes no sense to do this right now. So we'll just hit no. Nope. We don't want to do any of these things for now. Great. So hooks is basically what we just talked about. These are the typescript rip that run inside the gateway when lifecycle events files. So what this means is once we have this all live, there will be one typescript file that will run concurrently to everything that's going on. Hooks is how you set up that type rip file. This will make sense when we're doing the demo in a little bit. Again, as I was saying, everything is easily customizable after the fact. We'll just hit space to skip for now. Hit enter. And this is a really important step where it installs the gateway that we talked about. And finally, the moment we've all been waiting for. I just love that they say they're trying to hatch the board. I imagine a little dinosaur hatching. I haven't seen this in other tools that I've played around with. It's these little things that I appreciate so much. There is a web UI. I will be showing that in a bit. But for the full experience, we're going to be just using the hatch in TUI. So we'll hit enter here. And as it says, wake up my friend. And we'll have the first message from OpenClaw here. Great.

SPEAKER_01

[SPEAKER_00] So we're building this locally. Some people say you should build this in a VPS. Some people say you shouldn't. What's the truth about that?

SPEAKER_01

So really, it depends on two things. First, your usage. And second, your risk appetite. So I'll be candid. One of the things that I was trying to do, and we will be demoing that, is there is a secure folder that you can make called docs. And you can configure it to only interact with the documents inside the docs folder. However, when I was setting it up, I wasn't the most careful. And what ended up happening was on my Slack, it looked through all of the files that I had on my computer. And it answered a question with a response that it really had no business knowing. So that is really the criteria here. If you use a VPS, but if you use the cloud, you have that one layer of abstraction that protects it from making changes on your computer, on your local files. You forgo that privilege the moment you're not careful. I don't want to say that you're for sure going to be breaking things, but you owe yourself to be that much more careful and really know what you're doing, which is obviously our goal here with content like this. So hopefully, does that answer your question? Any follow-ups to that?

SPEAKER_01

[SPEAKER_00] So VPS, you can make it so your bot doesn't fall asleep. It can be a little bit more secure, but it doesn't have access to your local file system. And then also people use the Mac mini, which is a totally different computer. Of all of the three, I think Mac mini or different computer is the best, most recommended after that local, after that VPS. But look in your own situation for this demo, just continue with the local, I would say.

SPEAKER_01

Yeah. The only thing I would add to that is a VPS is actually also capable of making changes to your local or whatever. So VPS is, if we were to rank them in terms of risk, the riskiest, right? Because your computer need not even be on and stuff could be changing inside it and your bot could be actively creating or destroying things, running amok. So what we have here, what we're doing right now, and thankfully what happens by default is that the moment I shut my laptop, the bot refuses or it just falls asleep. So then we come back here. There's a command to wake it up again. And that's when things go live. So that is what I would recommend for most people. Again, there can be use cases where you don't, you're in a different room, you're in a different country and you want your computer to do something. It just depends. Yeah. To your point, Akash.

SPEAKER_01

[SPEAKER_00] Awesome. So quick note on in terms of what just happened here. So as you can see, it says I'm awake, but I'm in a bit of a blank slate. So random, I guess, little segue here. The way this is configured is it auto runs a file called bootstrap.md and it tells it what it is, right? That it's open claw. It has skills. It has hooks. It has a soul, a whole personality. And what it does then is that then it just disappears, leaving it in a dazed state. [SPEAKER_00] Awesome. So quick note on what just happened here. So as you can see, it says I'm awake, but I'm in a blank slate. So random little segue here.

SPEAKER_01

The way this is configured is it auto runs a file called bootstrap.md and it tells it what it is, right? That it's OpenClaw. It has skills. It has hooks. It has a soul, a whole personality. And what it does then is that it just disappears, leaving it in a dazed state. So which is why it's saying, so who am I and who are you? And this goes back to what I was sharing earlier with Peter's vision for this to force it to not just be whatever, chat GPT with no personality.

SPEAKER_00

[SPEAKER_01] It's just something that you've typed messages to. [SPEAKER_01] He really wanted to hard code the experience feeling like this is truly your companion and not just somebody that you go to with your problems. [SPEAKER_01] So we are going to be speed running this. [SPEAKER_01] We don't need to recreate the movie Her here, but I'll just say this is where I like to give it a name. [SPEAKER_01] So you can just say your name is, we'll just say fella, right?

SPEAKER_01

Because it's just something I like to say. So you can just be like, hey fella, can you, blah, blah. And then I'll say I am Naman, your lord. And I will try and spell my name correctly because that will be problematic if I don't. [SPEAKER_00] And how do you go backwards in the terminal? [SPEAKER_00] Some people don't know that. Yeah. So again, all arrow keys. And sometimes you can hit the up arrow to invoke previous commands that you've used. But as you pointed out, there's no such thing as a mouse. You're just completely reliant on your arrow keys. Great. So I'm just going to hit that. It's going to ask me a couple more annoying questions.

SPEAKER_01

I say annoying, but you know what I mean? I appreciate the idea. Okay. Yeah. So here's it. So it forces you to pick one of these three options. It can be a creature, a vibe or an emoji. Do you want to help me fill this out, Akash? Any of these looking good for you? [SPEAKER_00] It says just a really good fella. [SPEAKER_00] PM sidekick. [SPEAKER_00] Awesome. [SPEAKER_00] I like that. [SPEAKER_00] Is a proactive helper with no emoji signature. I said that 10X is my career. Act like you mean business. And no signatures ever. It's going to say something snarky if I were to guess, but we'll see. [SPEAKER_00] I've never actually run it in Gemini.

SPEAKER_01

[SPEAKER_00] So this is a little bit slightly different. [SPEAKER_00] I always use code. [SPEAKER_00] I'm excited to see this. Interesting. So look, pretty much this is live. We're ready to fire. We can get into, actually, this would be a good point to flash the UI.

SPEAKER_00

[SPEAKER_01] At this point, my first question is, is the gateway connected or not? [SPEAKER_01] Right? [SPEAKER_01] That's a perfectly normal question to have. [SPEAKER_01] Instead of fretting, I'm just literally going to ask it.

SPEAKER_01

Is our gateway live and connected? And the good thing is, if it's not, it will actually connect it for you. One time it needed a token for its gateway, which I did not know where to find. So I just asked it, where is the token? And it just gave me the token. So look, it says it's live and active. Perfect. So once you're done setting up, we hashed our bot. It will allow you to go to this front-end gateway, which is the UI version of the gateway, which lives on 127.0.0.1:18789. That's just the default port it uses. So this is what that looks like. I can just share a brief overview of what this all is.

SPEAKER_01

So the chat is really just the way you can communicate with OpenClaw itself. Usually, and as we discussed, the best way for it to do something is just ask it to do a certain thing. And it's really good at programming itself to do whatever you asked it to do, right? So that is still the biggest USP of why we want to use OpenClaw. That is the unlock that it brings. You don't have to sit and build all the components that you need. You just tell it that, hey, build this for me. And it almost architects itself, spins up other bots that it then manages. It does all of that autonomously for you.

SPEAKER_00

[SPEAKER_01] So all of that happens in the chat. [SPEAKER_01] This overview just shows your gateway token and such. [SPEAKER_01] Stuff that you need to know, everything that you've been doing. [SPEAKER_01] A couple other things. [SPEAKER_01] If you ever want to change what API you're using, so say you want to swap from Gemini to Anthropic for some reason, you can go into config. [SPEAKER_01] If you scroll down, you'll see this option called secrets.

SPEAKER_01

This will sometimes not open. That's totally normal. If you click raw, it'll show you what model you're using. So within Gemini, right, you know, we have one API key for all Gemini offerings. So if you want to use a faster model, you just have to change this out. Hit save, update. And that's how you can swap out your models and such. Having said that, as we know, you can also simply go on the chat and just say, hey, I want you to use model name, blah, blah, blah. And it will automatically program itself. So that section finishes the setup of OpenClaw itself. Now for our PMs, we want to obviously live and breathe within Slack. So we already set up our new app.

SPEAKER_01

We called it OpenClaw. You saw us do that. Now there are some important settings that we need to make sure we have before we can start talking to our bot. And that's how you can swap out your models and such. Having said that, as we know, you can also simply go on the chat and just say, hey, I want you to use model name, blah, blah, blah. And it will automatically program itself.

SPEAKER_00

[SPEAKER_01] So that section finishes the setup of OpenClaw itself.

SPEAKER_01

Now for our PMs, we want to obviously live and breathe within Slack. So we already set up our new app. We called it OpenClaw. You saw us do that. Now there are some important settings that we need to make sure we have before we can start talking to our bot, add it to Slack channels, have it read and write messages and such. We already did the two most important steps, which were the app token and the bot token. In addition to those, you want to make sure that when you go on OAuth and permissions, you should be able to see these bot token scopes.

SPEAKER_01

So the thing that's finicky with OpenClaw is that it doesn't tell you this right out of the gate that you need to do these things, which is somewhat understandable, right? Because most people maybe aren't trying to read groups or they aren't trying to look at what users are trying to do on Slack. So these are the three things that we will be using for all of the demo cases that I have prepared. It can very well be the case that something that you want to do needs a certain other permissions. Adding that is really straightforward. You just click that, mention whatever you want to add.

SPEAKER_01

The most key important thing here is no matter what you do in Slack when it comes to your app, you always want to click reinstall to your space because unless you do that, it will not work. It will not persist. So make sure that no matter whatever changes you make, you always reinstall to your space. Very rarely that makes this OAuth token change. It doesn't happen all the time. Very rarely it will change. In which case, make sure you just copy and paste it back to your OpenClaw gateway, which we had right here, and it will automatically update everything it needs to do in order for you to get to this OpenClaw within your app.

SPEAKER_01

That's just how so as you can see, I tested here. When you just say hi, it just responds to you. At first, it will ask you to use this key, which you, as we know now, we will just go back and paste that key. And once you do that, as you can see, it'll just come alive. Now from there, it's obviously very straightforward. It's simply a matter of adding it to whatever channels you want to add it to. Again, this is just some testing that I was doing here. But as you can see, you can just invite it to its channel and then add it. And then once you do, it'll be able to just lock and load right from that point. This section completes the setup of OpenClaw within your Slack.

SPEAKER_01

I'll pause real quickly. Akash, any questions that come to mind? Anything you want me to shed more light on? [SPEAKER_00] Before we dive deeper, let's talk about something every PM faces, getting alignment on product decisions. [SPEAKER_00] You know that feeling when you're trying to explain a user flow to engineering or justify a design choice to leadership and you're just describing it with your hands? That's where Mobin comes in. [SPEAKER_00] Mobin is the world's largest library of real-world mobile and web app designs from industry-leading apps like Airbnb, Uber, and Pinterest.

SPEAKER_01

[SPEAKER_00] Instead of spending hours taking screenshots or hunting for inspiration, you can instantly find exactly how successful products handle onboarding, paywalls, checkout flows, whatever you're facing. [SPEAKER_00] Over 1.7 million product builders use Mobin to benchmark against best-in-class products and show their team's proven solutions. [SPEAKER_00] Whether you need to convince stakeholders there's a better way to handle user activation or research a top app's approach for future discovery, Mobin gives you the visual proof to back up your product decisions.

SPEAKER_01

[SPEAKER_00] Check out mobin.com slash akash. That's M-O-B-B-I-N dot com slash A-A-K-A-S-H and get 20% off your first year. [SPEAKER_00] AI evals are one of the most important skills for PMs. And I know you know they matter.

SPEAKER_00

The question is, are you doing them right? Most teams are winging it with basic metrics and hoping for the best. Meanwhile, the teams that actually ship reliable AI, they've cracked the code on systematic evaluation.

SPEAKER_01

[SPEAKER_00] Today's episode is brought to you by the AI evals for engineers and PMs course by Hamal Hussain and Shreya Shankar. [SPEAKER_00] This live Maven course will teach you the battle-tested frameworks from Hamal and Shreya, who are the engineers behind GitHub Copilot's evaluation system and 25-plus production AI implementations. [SPEAKER_00] Four weeks, live instruction, next cohort starts July 21st. [SPEAKER_00] Start shipping AI that actually works. [SPEAKER_00] Enroll at maven.com with my code AG-product-growth for over $800 off. That's AG-P-R-O-D-U-C-T-G-R-O-W-T-H.

SPEAKER_01

[SPEAKER_00] I hope you're enjoying today's episode. Are you interested in becoming an AI product manager, making hundreds of thousands of dollars more, joining OpenAI, an anthropic? [SPEAKER_00] Then you might want to do a course that I've taken myself, the AIPM Certificate, ran by OpenAI product leader, McDad Jaffer. [SPEAKER_00] If you use my code and my link, you get a special discount on this course. It is a course that I highly recommend. [SPEAKER_00] We have done a lot of collaborations together on things like AI product strategy. So check out our newsletter articles if you want to see the quality of the type of thinking you'll get.

SPEAKER_01

[SPEAKER_00] One of my frequent collaborators, Pavel Hearn, is the Build Labs leader. So you're going to live build an AI product with Pavel's feedback if you take this AIPM Certificate. [SPEAKER_00] So be sure to check that out. Be sure to use my code and my link in order to get a special discount. [SPEAKER_00] And now back into today's episode. [SPEAKER_00] When I use OpenCall in Slack versus the TUI dashboard that we're seeing and the other tab, are there any limitations or is it fully featured in Slack? Great question. So the way to think about the TUI and this UI dashboard, so we can just call it the gateway dashboard because that's what OpenClar likes to call it.

SPEAKER_01

So what you'll see is that whatever you talk about over here [SPEAKER_00] If you take this AIPM Certificate, be sure to check that out. Be sure to use my code and my link in order to get a special discount. And now back into today's episode. When I use OpenCall in Slack versus the TUI dashboard that we're seeing in the other tab, are there any limitations or is it fully featured in Slack?

SPEAKER_01

Great question. So the way to think about the TUI and this UI dashboard, so we can just call it the gateway dashboard because that's what OpenClar likes to call it. So what you'll see is that whatever you talk about over here will automatically get reflected in the terminal UI as well. So it's the same thing. There's really no difference. So hopefully that answers that part of the question. These two are the same things. Most people will want to use this just because of the benefit that pasting images unlock when you're talking to any LLM, right? It's just worth a thousand words, especially in this case. So that's where so you can think of this as your control center, your command center, if you will. What I mean by that is as we were seeing here, I was running into some issues with setting this up in my channel, right? So to troubleshoot that, where am I going to go? It's not going to work if I ask OpenClar on Slack to fix itself. So we need to go back to our control hub, which is this gateway dashboard. So really, suppose we were trying to do WhatsApp as well, right? You can ask OpenClar on Slack to set up your WhatsApp for you. Actually, as I say that, maybe it will be able to. But even for that, you'll need an entry point. So really, this gateway dashboard is an entry point to any and all of the other apps that you want to leverage. OpenClar on, be it WhatsApp, be it Slack, be it Telegram, all of those things. The first hub that you go out into the world is still this. Does that answer your question?

SPEAKER_00

Yeah. So are we fully set up? Are we ready to see it in action?

SPEAKER_00

[SPEAKER_01] We're ready to see it in action, actually. And there will be some other things that we'll be learning. But the way I have it constructed is we can just go through them as we go through our use cases itself. So with that, I'll launch into use case one. And as is tradition on your channel, we will be leveling up, right? So we'll start with dipping our toes a little bit, just exploring what's possible. And then for the final use case, I have something that hopefully will leave at least some of your viewers' jaws on the floor. That's my goal with all of this. So yeah, let's just jump right in. So use case one, and I can throw this on the screen as I talk through this. So use case one is that we're going to turn any Slack channel into an AI powered knowledge base that answers team questions from your product documentation. So what we'll be doing is we'll be dropping our PRD, FAQ documentation, any product wiki into the workspace folder, which I'll show you where that is and how to find it. And then anyone in the channel can simply mention the bot to get instant contextual answers. Why should PMs care? Because it simply eliminates the product questions channel problem where PMs have to spend hours answering the same questions about feature specs, launch dates, and edge cases. Again, it's important to note here that this repository is not locked in. It lives and breathes as a living space. You can add and remove stuff to it. The memory persists. So if you ask it, hey, what is an FAQ that we added three months ago that wasn't there six months ago, it will be able to tell you that, right? Because it's not just locked in time. It lives and evolves with you. So we will be building this out for our first use case. So now as we do that, the first question that naturally is probably arising for our listeners is what is this workspace that I mentioned? So this is tied in perfectly to the really cool capabilities of OpenClock because I'm sure at least some of you are wondering what exactly is the USP or the use case for using OpenClock against Slackbot, right? Because if it's just answering questions on a channel, Slackbot could probably be configured to do that as well, right? Here's the difference. Slackbot does not have access to local files that live on your computer. Neither does it have the ability to read or write into those files. So this folder here, which is just called .OpenClock, and some of you will struggle in trying to reach it. So I'll show you a quick tip on how you can easily access it. So if you click your little finder icon, right click it, sorry. And then if you go to go to folder, if you just press a period, it should show you an option to go to OpenClock. This is really annoying because it doesn't, it's not a folder that you can just go to, at least not on my computer. So it took me like ten minutes to figure out how to get here. But now if you simply click that, it will take you straight to this folder that we have here. Now yours will not look like this exactly because I've been, as I said, playing around with it a decent amount. What you need to know is this workspace component. This you will find already pre-setup for your own computer. As soon as you install OpenClock with some of these files, such as agents, heartbeat, soul, tools, memory, and user. What are these? I have these written here. Soul MD is your personality or values. Identity is the agent identity. User is just all of your preferences, which in my case, as we saw, we had it be really direct, not beating around the bush, super to the point. Memory is stuff that persists. So even when you close your bot, you shut your computer down, this stuff still continues to be alive. And then tools are your local configuration nodes. And finally, heartbeat, which is really important, is a list of all of your cron jobs that it signals that, hey, now is the time to run this recurring task. So I can just open one of these just for you guys to look at.

SPEAKER_00

[SPEAKER_01] Identity is the agent identity. [SPEAKER_01] User is just all of your preferences, which in my case, as we saw, we had it be really direct, not no beating around the bush, super to the point. [SPEAKER_01] Memory is stuff that persists.

SPEAKER_01

So even when you close your bot, you shut your computer down, this stuff still continues to be alive. And then tools are your local configuration nodes. And finally, heartbeat, which is really important, is a list of all of your cron jobs that it signals that, hey, now is the time to run this recurring task. So I can just open one of these just for you guys to look at.

SPEAKER_00

[SPEAKER_01] So we'll look at heartbeat. [SPEAKER_01] You can simply open with sublime text. [SPEAKER_01] Otherwise, it tries to open Xcode, which is annoying. [SPEAKER_01] Some of you might not have that.

SPEAKER_01

But look, this was all pre-setup. This is something that I set up. So this you will not have. So originally your heartbeat.empty will be empty, right? Because you don't have any activities that you wanted to do automatically. One other cool thing about this is if you go back to your gateway dashboard, and if you go to cron jobs, here is also a really cool way to see all of the activities that you have running along with the ability to edit or modify it. So we'll be going over a use case for this in just a minute here. But for now, as we were discussing, we wanted to have a repository for our files where we can throw our documents and then query the Slack channel.

SPEAKER_01

So in my case, I simply just made a document or a folder called docs. Once I go into it, it has this PRD document, which I can flash. The made-up slash semi-real product that we'll be working with through these demos is something that I'm actually working on. It's really just a one-click setup of websites for podcasters just using their RSS feed. So that's my whole big idea. You just submit your RSS feed. It gives you a fully functional, really nice-looking website. So what I did was I just generated a PRD for that. As you can see, it's pretty run-of-the-mill stuff. And I threw that here.

SPEAKER_01

What I have not done is I also have this file called an FAQ, which I had not added to this folder yet, but that I'm going to in front of you. So my goal here is to demo that even though this file was just added to this, it will still work and it will continue to do its thing, right? So I just, as you saw, drag this over here. I'll make sure to rename this in a way that it can read that hopefully. Will it enter? Will it add? Great. So now our initial document setup is ready. So as we talked about, we will now be querying our bot. And you can do this on any channel or you can do it directly. It really doesn't even matter.

SPEAKER_01

But maybe we'll just use a channel that I'd added it to, right? Or maybe we'll go to bug reports. Really, it can be any channel that OpenFlow is added to or just the directly OpenFlow channel itself. So we'll go here. We'll say, look through the docs in your workspace folder and tell me the... I actually even had a question ready for this. So let me pull up that question. It should be right here. Yep. So I wanted to outline the database schema for handling this RSS and AI data. So I'll just simply post that. So we will run this. I expect it to... Oh, and remember, guys, you always have to tag it. Otherwise, sometimes it can be iffy.

SPEAKER_01

So just to be sure, I'm going to resend with having tagged it. Although I do think it should work, but we'll just resend it just in case. And now we wait for it to respond. [SPEAKER_00] So what do we expect to be doing in the background? Yeah. So great questions. Okay, great. So as you can see, it's churning out some stuff. So yeah, Akash, what it does in the background is that it goes into its root folder. It knows that docs exists there. It can see inside it to find whatever it needs, right? So then it looks through that document and then comes back to the original request. And then in this case, it answered my question based on the doc that it found.

SPEAKER_01

Let's test and make sure that it found the FAQ that I just pasted in as well. We'll say, are there any FAQs that we missed in the FAQ doc? My plan is whatever it comes up with, we'll actually have it write to the doc itself, just using Slack without me lifting a single finger. So let's see how it fares with that. [SPEAKER_00] So it has access to docs and can edit them if they're in Markdown. Exactly. That's exactly right. Realistically and technically, it has access to every file on your computer. Right now, it doesn't look interesting. So it did find the FAQ.ext without me telling it explicitly that I just pasted that in, right? So it found those things.

SPEAKER_01

Look, it even offered me, I can append these. Let's say, sure, let's do that. So the important thing outside of this little toy demo here for your listeners is that these can all be lifetime. Remember, I am right now sitting here doing these things, but it can very well be that maybe one of your leaders or one of your customers reach out saying, hey, this is a question I have. Why is this not on your FAQ? Maybe you can even get an email on this and that is actually subject for the next use case, but you can have it set up to be automatically making doing these operations in real time. So apparently it seems to have added it. So we'll go back to our thing here.

SPEAKER_01

It even added the SQL schema that I'd asked it to just to make sure that I can access it later outside of Slack as well. So if I open this file now and I'm now realizing it would have helped to show a before after, but hopefully we can see any differences in the way they're written. Yeah, they even labeled it with additional features and infrastructure. And it added those four questions that it thought that it should have. But you can have it set up to be automatically making doing these operations in real time. So apparently it seems to have added it. So we'll go back to our thing here.

SPEAKER_01

It even added the SQL schema that I'd asked it to just to make sure that I can access it later outside of Slack as well. So if I open this file now and I'm now realizing it would have helped to show a before after, but hopefully we can see any differences in the way they're written. Yeah, they even labeled it with additional features and infrastructure. And it added those four questions that it thought that it should have. So again, going outside of the toy example, you can have dozens of files in this folder, right? This is not limited to just one PRD and one FAQ.

SPEAKER_01

It has the ability and the context to sift through all of them and really customize its responses to what it's seeing in that folder. That concludes demo of use case one. Before I launch into the second one, do you have any questions, any clarifications that I can do? [SPEAKER_00] So I see this as an instant knowledge base. [SPEAKER_00] This is about if you can construct a really strong repo of, hey, these are the features we're going to build. [SPEAKER_00] This is the strategy.

SPEAKER_00

These are the transcripts of every customer conversation. These are all the relevant data charts. You can scale your impact. And the flow can be that your engineers and designers, they go out there and they come up with a future idea. They chat with your knowledge bot to come up with the proposal. Then the human actually comes in and actually reviews it. And the PM can actually really scale their impact this way. So with the way ratios are going, PM supporting more engineers than ever. I see this as a really important tool to multiply your leverage.

SPEAKER_00

[SPEAKER_01] Not only is that a great call out, but the aspect of that, that you mentioned where you can build that repository. [SPEAKER_01] I would put a little asterisk in that and say that you actually don't even have to build that repository. [SPEAKER_01] OpenClaw builds that for you, which it's funny you say that because that is exactly what use case three is. [SPEAKER_01] But for now, for use case two, what I had was the pain point quote unquote being, which I will paste here again. [SPEAKER_01] And you know, I know enough PMs to constantly hear about this being a huge pain in their behinds. [SPEAKER_01] And honestly, even software people.

SPEAKER_00

[SPEAKER_01] So automated daily standup summaries. [SPEAKER_01] What it does? [SPEAKER_01] Every morning at 9am, OpenClaw scans your team Slack channels. [SPEAKER_01] These can be as many channels as you want. [SPEAKER_01] It summarizes what happened overnight, identifies blockers and posts a concise standup brief to product standup. [SPEAKER_01] Why should PMs care about this? [SPEAKER_01] Because it replaces the 15 minute context gathering ritual. [SPEAKER_01] I actually saw a post on LinkedIn just earlier today where somebody was like the bane of my existence is on every Monday.

SPEAKER_00

[SPEAKER_01] I have to sift through all of what happened last week and compile that to share on my weekly standup. [SPEAKER_01] So you walk into your first meeting already knowing what shipped, what's blocked and what customers complained about. [SPEAKER_01] Before I launch in any thoughts on, you know, this particular use case, would you agree that this is kind of a pain point for PMs? [SPEAKER_01] It would be helpful if you can add your take to this. Yeah, sounds great. Looks, especially if your teams are reporting into Slack channels and if they're not reporting into Slack channels, we can configure other data sources, which I think we'll cover in a bit.

SPEAKER_00

But if they are in Slack, this is perfect. [SPEAKER_01] Perfect. [SPEAKER_01] Yep. [SPEAKER_01] So as you can see, in this case, I have a engineering channel setup and a design. [SPEAKER_01] So what I was hoping to do, and you can, you know, you can tell me if this is a bad idea, was for you to even have an addition to me, just write tough here that, you know, this broke, this doesn't work. [SPEAKER_01] I'm going on leave or whatever you will. [SPEAKER_01] So our goal is to really confuse it. [SPEAKER_01] If you know what I mean, and then we'll run the cron job.

SPEAKER_00

[SPEAKER_01] And by the way, because I was testing it, you can see the morning standup summary that dropped sharp at 8am my time because I'm CST. [SPEAKER_01] So, you know, it did its job, but obviously it's not limited to just 8am. [SPEAKER_01] We can even run it whenever we want, right? [SPEAKER_01] So would, what do you think if I invited you here? [SPEAKER_01] Akash, would you help me spam this? [SPEAKER_01] Here, I'll grab your email and we can blur out your email. [SPEAKER_01] But I thought this would be a fun activity. [SPEAKER_01] We will directly add you to npspace. [SPEAKER_01] Great. [SPEAKER_01] And while that happens, I guess I'll add you to design as well.

SPEAKER_00

Let me know if you were able to access. [SPEAKER_01] But in the meantime, I'm just going to start, you know, we'll just pretend this is an actual engineering Slack channel. [SPEAKER_01] We'll say, or guess, I guess I'll say I'm going on leave starting tomorrow. [SPEAKER_01] So my sprint will be extended by two days and we'll just, and I'll just hyphenate and say my name just so it knows. [SPEAKER_01] And then for design, I'll say, the back button is broken and I don't know how to fix it without talking to my design lead.

SPEAKER_01

[SPEAKER_00] Okay. [SPEAKER_00] We'll just send that. Right. So we're obviously just trying to, you know, yeah, exactly. Just a bunch of updates come in all day. And as I showed you on the product standup, this will be generated tomorrow morning when we are no longer on the call, but we'll just have it generate now. Right. So for that, I'll just say open clock. Yeah, so one important thing here, you can obviously ask it to generate the morning standup summary. The other thing you can do to set this up is, and I guess I can now show you guys how you can do this, but the way to do this is set up a cron job. And this is what that looks like.

SPEAKER_01

So you just go on your chat and you just mention that the following command, right? So what I like to do is go on whatever Claude or what have you, and just type out in simple English that at 8am, I need to know blah, blah, blah. Basically the problem statement that I just shared. And yeah, so one important thing here, you can obviously ask it to generate the morning standup summary. The other thing you can do to set this up is, and I guess I can now show you guys how you can do this, but the way to do this is set up a cron job. And this is what that looks like.

SPEAKER_01

So you just go on your chat and you just mention that the following command, right? So what I like to do is go on whatever Claude or what have you, and just type out in simple English that at 8am, I need to know blah, blah, blah. The problem statement that I just shared. Now you can even paste that here directly. What it will do is it will automatically convert those English instructions to system readable code, quote unquote, if you will, which, what does that look like? The following set up a cron job. That's the command for that.

SPEAKER_01

This 09 stuff refers to the time zone session isolated message. It, yeah. So it reads the last 12 hours in those two channels. You can add a certain channel here. If these aren't enough and it will summarize what shipped, what active blockers or escalations, key customer complaints, right? And then post a summary too with clear headers. What you can also do is have an associated catchphrase for this to trigger. Just a Iron Man style. If you use Whisperflow, you just press your little activate button and you just say standup and you just hit enter. And it does everything else for you, which is really cool.

SPEAKER_01

So I'll just be trying to demo that here. So I'll just say standup and we'll make sure there's no space. And we'll see if it's able to run the cron job and give us all of these new updates that it now has. So fingers crossed. [SPEAKER_00] Product managers are getting one closer, one step closer to Iron Man. Okay. So tell me if any of this feels accurate because you inputted some of those things. Five features have been shipped. Three new templates have been shipped. There's a few blockers. UI development is on leave. Unable to fix broken back rate. I'm also going on leave extending by two days.

SPEAKER_01

So, I mean, again, I don't think anyone is surprised here. Oh, if this surprises anyone, it's because of testing that I was doing earlier. But yeah, you no longer have to comb through a bunch of Slack channels. And as you will see in our next use case, even stuff outside of Slack, it just constantly lives, breathes. It's pulling all of these various avenues and then consolidating them for you to just be in your own bed and not even have to join the call, whatnot. And just be relaxing. Not that that's what PMs do.

SPEAKER_01

[SPEAKER_00] But yeah, we all live in Slack hell with way too many messages and notifications. It's impossible to keep up. So now you have somebody who's there that you can converse with basically and get caught up on Slack. Actually, on your point around the conversing, we can even ask it what's here that needs my immediate attention, right? Because if you're trying to not get overwhelmed by all of this stuff going on, it is smart enough to figure out what you need to immediately act on. In this case, I'm hoping it will bring up this print stuff because that's a big blocker in my view.

SPEAKER_01

Yeah, exactly. Right. So you're going on leave. Also notice how it knows that Naman is me. So it didn't say Naman here, it said you. Ensure your tasks are handed off or documented.

SPEAKER_00

[SPEAKER_01] Anyway, we don't need to check its work. But what's the takeaway here is that unlike other LLMs, right, which constantly lose memory, run out of context size, run out of token windows. This is built to constantly make sure that it regurgitates the right context size to not lose sight of what's important here. That's really the headline here and not the nitty gritties of what we have here. [SPEAKER_01] So before I move into use case three, just wanted to pause. Any thoughts, questions, anything else that's coming to mind with this? Let's move on to three.

SPEAKER_00

[SPEAKER_01] Perfect. So for use case three, we have the following. What this is, is really competitive intelligence pipeline on autopilot. It basically monitors all of your competitor avenues. Right now, this just says websites, Captera reviews, product hunt launches, hacker news mentions. You can have this list be 15, 20 items long, right? There is literally no stopping this.

SPEAKER_01

What it does then is that it synthesizes a competitive intelligence brief using SWOT analysis and it posts it to a private competitive intel Slack channel.

SPEAKER_01

Why should PMs care? It's because obviously doing all of this manually is really critical. In addition to that, say there were certain changes six hours ago on a competitor website, you happen to be sleeping, right? When you woke up the next morning, they had overwritten that for change C instead of change B. In a normal world that is gone forever, you have no way of ever finding out that that happened. Not with this, right? OpenCloud never sleeps. It's just out there, doing its thing, monitoring it every hour, every half hour, if you can set up to do that. And then, yeah, that competitive brief lands in your Slack without anyone lifting a finger.

SPEAKER_01

So the way I want to show this here is by actually building this out. So I did not, in fact, end up building everything because I did want to show what the building looks like. So really what we're doing is what I just said, right? We go on here, remove that. And I have the prompt pre-ready just because I didn't want to waste time.

SPEAKER_01

But in your competitive intel Slack channel, just mention the bot with something like I need blah, blah, blah. Search the web. And I customized this to our use case, which was latest news, product updates, and user sentiment about pod page, which is, and transistor FM, which are my competitors for the toy example. Toy slash serious example that I was trying to build. Organizer findings highlight anything that represents a threat or opportunity. For a mid-market podcast website builder site, poster analysis will say there. We go on here, remove that. And I have the prompt pre-ready just because I didn't want to waste time.

SPEAKER_01

But in your competitive Intel Slack channel, just mention the bot with something like I need blah, blah, blah. Search the web. And I customized this to our use case, which was latest news, product updates, and user sentiment about pod page, which is, and transistor FM, which are my competitors for the toy example. Toy slash serious example that I was trying to build. Organizer findings highlight anything that represents a threat or opportunity. For a mid-market podcast website builder site, poster analysis will say there. So what is going to happen is, first of all, it will say there is no competitive Intel Slack channel. And it will make us do all of that rigmarole.

SPEAKER_01

So let's actually build this out so you guys can see what exactly that looks like. While it does that, we can simply make that channel right, make sure we have the right name. So we'll simply just copy that, make that channel, hit next. You can just have it be public. Great. We'll just add everyone. And then I guess we'll also add the app because I don't think that is added. Yep. Great. So we did that. It's still thinking. We'll give it some time to think some more. [SPEAKER_00] So when you want to look at the context and that it has, is there a way to look at that? [SPEAKER_00] Because I know with Cloud Code, managing the context is a really important part. Yeah.

SPEAKER_01

So a big part of the context lives on these files itself. So for instance, if I showed you agents, right? Like what are the agents that it's working with? So I'll flash it up here. So this is, you can think of it as its consciousness, if you will, right? So this has everything that it needs to run. So for safety, this is just all default. So don't exfiltrate private data. Don't run destructive commands, so on, so forth. Ask first, right? So for anything sending emails, tweets, publics. Again, this is just boilerplate. You can change all of this.

SPEAKER_01

So the way to work this is you can go on your Cloud or Gemini, whatever, and then have that build out the entire markdown document. Suppose you want five different agents that Fela, in our case, leads. So you can have that organizational map that bot A will just say, Naman, is responsible for marketing. Bot B is responsible for so on, so forth. And then if you just paste that markdown file into your workspace here, it will know exactly what you want it to do at any given point, right? So that is the way to manage not just what you want it to do, but also what you want it to work with in terms of the documents and such.

SPEAKER_01

[SPEAKER_00] And in terms of those documents, agents, so what are the best practices? [SPEAKER_00] What goes in what document? Yeah. So the good news is that this will all be set up for you by default. You will not have to worry too much about changing a lot of things. Again, if you were to want to change this stuff, there is a line here that always makes me feel philosophical. But I forget exactly where it is. Remember what I said about the stand-up stuff? And this is not something I've written. This, it wrote itself. So if Naman types the exact words stand up in any context, he must use the message to, instead of replying directly, call message with action read.

SPEAKER_01

This is all my Slack channel stuff. So it configures itself to act according to how you want it to. [SPEAKER_00] Nice. [SPEAKER_00] So you could just chat with it and it'll update those files over time. Yeah, that's exactly right. Perfect. So it did its business. It actually started doing the analysis first, which is not something I was expecting. So this error around the missing Brave key is, Brave is really just an API that any agents do, even if you use Cloud Cowork or now today ChatGPT came up with their entire task-based thing. But it really makes it simple for agents to browse the internet. So we can set up Brave API key. That's straightforward enough.

SPEAKER_01

But for now it says, it didn't find the channel, which is something that we had forecasted. So what we will do now is, firstly, we have this channel. So something you need to do to point it to your channel is go on here. And if you click channel details, over here you'll find the channel ID. So you can just simply copy that. Go here and say, the channel ID is that. And then as we just talked about, it will configure itself to be able to talk to that channel and such. Now while it does that, we can go ahead and do the Brave API key setup. This is important because pretty much any type of web browsing activities that you're going to be doing will involve this.

SPEAKER_01

I believe it starts at $5. Yeah, I think that was where we had started. So I think I already should. Okay, I do have an account. I don't think I have an API key. So I guess I'll just configure this up real quick. So we have our API key. We'll just add that. We'll just say open clock. We'll hit add searches. There is fine. That's our guy. We'll copy that. Go back here. Great. So I successfully posted that message. We can verify. So if we go back. Great. So it was able to do that. All it needs is an API key now, right? Everything else is ready to go. So we just come here and we say Brave API key is.

SPEAKER_01

And this can stay because I'm going to delete this immediately after. But the important takeaway here is normally for anything else, what you would have to do is go into your VS Code file, go into your environment variable, paste the API key, then attach that variable to anywhere else in the code where you would need to access it. Here you just dump it on your nice little interface, and it puts itself to use. All it needs is an API key now, right? Everything else is ready to go. So we just come here and we say Brave API key is. And this can stay because I'm going to delete this immediately after.

SPEAKER_01

But the important takeaway here is normally for anything else, what you would have to do is go into your VS Code file, go into your environment variable, paste the API key, then attach that variable to anywhere else in the code where you would need to access it. Here you just dump it on your this nice little interface, and it puts itself to use, and it pastes the API key everywhere it needs to without you having to lift a single finger. Sweet. Yeah. And the reason it disconnected is because it needs to refresh. And I think that's the API response. If I'm not mistaken, apparently it did it. So we'll say, we'll just say, run the competitive analysis right now.

SPEAKER_01

And we'll hit send. And then we should see a message here. Actually, what I should have done was write that prompt here, but it's really the same. You can use them interchangeably at the end of the day. They're all going to the same source, if you will, even though the avenues are different. Great. So as we know, it is smart enough that it knows that it's supposed to go there. So, okay, let's look at the analysis. So I actually use PodPage and I've used Transistor as well.

SPEAKER_00

[SPEAKER_01] So let me quickly just eyeball this and see if it's looking accurate.

SPEAKER_01

Aggressively targeting podcast. Okay. That's accurate. Allowing multiple shows. Yep. That's true. Many built-in sites are rudimentary. Yep. I mean, I can show my site that's on PodPage and it's just the worst. Sorry, no shade, PodPage. Migration tooling. Since PodPage relies on a wide glove, Seamless could be a massive conversion driver. This is gold. So I'll show you what I have been working with.

SPEAKER_00

[SPEAKER_01] This is my very rudimentary pre-MVP stage.

SPEAKER_01

Something I had not thought about so far was exactly how to make it really easy for other folks to import their pages into this. So this is just what I have right now. And my plan was to go away from the whole WordPress type route. So it did accurately identify this super cool, at least to me, angle or wedge here that it could be a massive driver to seamlessly allow people to go from WordPress to platform migration in terms of opportunities. Video integration. Video integration. This is one of the biggest reasons why I even had this idea. And I have that, or at least I'm working to have that be built in because most podcasts now are video enabled. Right?

SPEAKER_01

So I wanted this to be video first. So I have not seen this before. This is the first time I'm seeing this in work. And at least I'm definitely impressed by what it's saying. Let's look at risks. They are pushing native network websites, reducing the need. That's a fair call out. If hosting platforms improve their native site builders, standalone will lose market share. Perfect. So, I mean, in a sense that does conclude our demo, but what's important here. [SPEAKER_00] One question I have is any AI tool you ever build, I've had AI agent CEOs like Lindy and Relay, you and I did the agent browsers. [SPEAKER_00] People talk about Cloud Code and co-work.

SPEAKER_01

[SPEAKER_00] They always use this comparative analysis use case. [SPEAKER_00] So how does Open Cloud differentiate from all those other AI tools? I would say the biggest differentiator. And at least I know for a fact that this is not possible to do using any of your AI first browsers. Definitely not when we are recording this on 5th March 2026. But the biggest takeaway here or the wedge, if you will, is that first, we don't have VPS set up right now, but you can have it be polling Google reviews.

SPEAKER_01

You can have it be polling a bunch of different avenues that it would just be really hard for any other or even Cloud co-work for that example, to look at actively every 30 minutes and then persist with its memory. So that six months down the line, if you asked it to say, generate a trend line of all the changes that a certain competitor made that helped or hurt their business when it came to reviews on Reddit or on Twitter, it's having a watchdog across any website that you can think of that literally never sleeps.

SPEAKER_01

And along with the ability of it being really smart and you being able to converse with it in real time in a way that it never forgets a single update it saw 7.30, 5.2 hours ago at 1 a.m. when you were randomly sleeping. I will say with co-work, the difference is a little bit lesser.

SPEAKER_00

[SPEAKER_01] For me, the differentiator then becomes cost because remember, you can run Quen 3.5 on this. [SPEAKER_01] Quen 3.5 is one-tenth the price of Anthropic APIs. [SPEAKER_01] I am mortally afraid of ever using Anthropic APIs because one prompt and it burns through $20. I don't know if you've had a similar experience, but when you couple similar-ish abilities with the ability to be really agnostic with your AI LLM usage, I do think that's the democratization of it all that really makes it click together. [SPEAKER_01] And for me, I actually don't even do a bunch of things just because of how expensive it is with co-work in particular.

SPEAKER_00

[SPEAKER_01] I'm actually afraid to use co-work, but not with this, right? [SPEAKER_01] Because Quen can get you, per my experience, at least 60-70% of the way there for one-tenth the cost. [SPEAKER_01] And for most people I'm willing to wager, that's a fair enough trade-off. Okay. And you mentioned about the VPS part of that. Can you say more on that? [SPEAKER_01] Yeah. [SPEAKER_01] So you can have this be doing operations within your file system when your computer isn't even on or when it's shut down. [SPEAKER_01] You've shut down your computer and it still will be able to do things without actually you being around or being in the same country.

SPEAKER_00

[SPEAKER_01] Again, that is risky.

SPEAKER_01

Because Quen can get you, I would say per my experience, at least 60-70% of the way there for one-tenth the cost. And for most people I'm willing to wager, that's a fair enough standoff or trade-off, I should say. [SPEAKER_00] Okay. [SPEAKER_00] And you mentioned about the VPS part of that. [SPEAKER_00] Can you say more on that? Yeah. So you can have this be doing operations within your file system when your computer isn't even on or when it's shut down. You've shut down your computer and it still will be able to do things without actually you being around or being in the same country. Again, that is risky.

SPEAKER_01

I have not, I'm just personally worried to play around with it. I was trying a bunch of WhatsApp initiatives yesterday with OpenClaw. It decided to message everybody that I was talking to for two hours after I'd done my demo, just with trying to pair with their phone numbers. So I would say, nothing I ever did would have prompted it to do that according to my brain at least. So I was talking to my mom and it auto sent her. And firstly, I asked it, do you have access to my other chats? And it said no, I can only chat with, you know, how you have your own chat on WhatsApp. I was like, great.

SPEAKER_01

Except clearly that's not true because it sent her the secret code to attach to her number as well. And my mom was like, what is this? What is going on? And I was like, don't worry about it, mom. [SPEAKER_00] Okay. [SPEAKER_00] So beware connecting your OpenClaw to your work Slack and your WhatsApp. [SPEAKER_00] It can go off and do autonomous crazy things. [SPEAKER_00] So you need to do it in a safe way. I will say to just caveat with Slack and with any, here I'll put it this way. Any default things that you're doing are probably fine. I've not seen it misbehave on my computer so far.

SPEAKER_00

[SPEAKER_01] Not that I can see, at least nothing that I've noticed. [SPEAKER_01] So for most use cases, you are probably fine. [SPEAKER_01] But just remember that it comes built in with most security guardrails in place. [SPEAKER_01] And just make sure you're not trying to move them around unless you have a really strong reason. [SPEAKER_01] Or if you really know what you're doing.

SPEAKER_01

For most people, for most use cases, if you stick to the default guardrails it comes with, I think, and please don't quote me on this, but you will probably be fine. With Slack and such, you don't have a lot to worry about, right? Because the moment you start to worry, you just disconnect it, right? It's literally a one-click operation to delete this app from your Slack. And you're good, right? It's as simple as that. [SPEAKER_00] But I will say... [SPEAKER_00] Famous last words. [SPEAKER_00] Famous last words. [SPEAKER_00] I think it was the Meta Super Intelligence safety lady on Twitter. [SPEAKER_00] That's true.

SPEAKER_01

[SPEAKER_00] She posted about how she had to run to physically unplug her OpenClaw from deleting her emails or contacts or something like that. It's true. Yeah. And it's funny you bring that up because to do that, OpenClaw would need, that's right, Brave API, which we just gave it, right? And I do have a use case around that as well. With that concern with email. But it's a good point. Now, I guess what's not reported is she probably taught it or asked it at some point to do delete related operations on her email.

SPEAKER_00

[SPEAKER_01] I'm not trying to victim blame here, but you know, we can go on.

SPEAKER_01

But that's just my two cents on the topic. [SPEAKER_00] So, while we're talking about it, we have to give people the guidance. [SPEAKER_00] How do they launch OpenClaw safely, securely, implement the stuff we've been teaching them so far without being worried it's going to WhatsApp their mom a secret key or delete their emails? [SPEAKER_00] Beautiful. So, the way I like to do this is instead of guessing, let's just simply go to the source of the problem, which in this case is also the solution.

SPEAKER_01

So, we will directly say, based on the way you are set up on my machine, I need you to do a thorough analysis of security vulnerabilities and tell me where I am at risk and what we need to do to fix things.

SPEAKER_00

[SPEAKER_01] Do not make any changes. [SPEAKER_01] I'm just looking for direction here. [SPEAKER_01] The good news here is that it doesn't know how to lie to you yet.

SPEAKER_01

So, it will just tell you. But I'm so glad you brought up this question, Asash, because no two cases are the same. And I really encourage people that are dabbling in this to consistently run this. You can even have a cron job for this every week so that it automatically tells you that, hey, last Sunday when you were playing with email, you left this on. This could be a problem. Let's switch that off. So, it's really just hygiene. In the industry, we call it security hygiene. And thankfully, in this case, there's an easy way to do that. But I am actually curious to see what it tells me because I have been, according to me, pretty reckless. So, we'll see. Great.

SPEAKER_01

We'll let it load here. Yikes. Firewall is disabled. That's never fun. Okay. So, yeah. A bunch of risks around Slack, which in my case obviously makes sense because this is my toy Slack. I'm not actually doing stuff. Unrestricted file system access. All of this stuff needs to be fixed. So, if a malicious or rogue user in Slack tells OpenClaw to read your personal Mac files, it will likely execute it. Which is interesting because you're on my Slack. So, you could just ask it that, hey, what's Naman's personal bank statements looking like? And it will probably respond to you. So, yeah. No good. Right? We definitely do not want that.

SPEAKER_01

Inbuilt application firewall is completely turned off. I think that's literally a no-brainer to switch it on. Again, we can keep going. It came up with the remediation plan. And you can even choose what degree of paranoid you are. So, I can literally tell it that I'm extremely paranoid. So, you could just ask it that, hey, how much, what's Naman's personal bank statements looking like? And it will probably respond to you.

SPEAKER_00

[SPEAKER_01] So, yeah.

SPEAKER_01

No good. Right? We definitely do not want that. Inbuilt application firewall is completely turned off. I think that's literally a no-brainer to switch it on. Again, we can keep going this. I told you, it came up with the remediation plan. And you can even choose what degree of paranoid you are. So, I can literally tell it that I'm extremely paranoid. I don't even want to take the slightest chance of something going rogue. So, just change all of your settings to match that. And it will do it. You don't even have to go around snooping into its stuff for it to figure that out. It will just clear itself, so to speak. Sweet. All right. Let's move on to the next use case.

SPEAKER_00

[SPEAKER_01] Great. [SPEAKER_01] So, this next use case is something that we've hinted on here and there through our chat. [SPEAKER_01] So, now in this case, instead of just Slack, we'll be moving away from Slack support channels. [SPEAKER_01] I mean, we will have those.

SPEAKER_01

But in addition, we'll also have forwarded emails. We'll have intercom transcripts if you need. We can even have Google reviews, Reddit threads, whatever you need can all be thrown into this together. And what the goal here, especially if you have a product that is fairly new, it's very, you're trying to iterate really quickly. What you can do is that it generates a voice of the customer report posted to Slack. So, then PMs can mention the bot to drill into any theme as well, right? So, tell me more about the authentication-related complaints this week. Maybe because on your stand-up, somebody reported an unrelated issue related to authentication.

SPEAKER_01

So, now you're wondering, could something have broken that we just don't know? Well, the easiest way is to just poll what your customers are saying, right? Why should PMs care? Because this is the PM dream. A living queryable customer feedback system that doesn't require an analytics platform. The bot maintains persistent memory. So, it tracks trends over weeks, which is something that I was mentioning before. And it can also tell you authentication complaints. Increased 40% compared to last week. And again, this is extendable to quarter, year, even probably five-year time frame. So, the persistent memory is the key aspect to this.

SPEAKER_01

And as we were talking about it, we have a memory file, a markdown file right here, which it makes sense to flash, which right now just has this. But, sorry, wait. I think for the persistent memory, okay, yeah, it is memory.md create. So, it's always helpful to check. So, when we are done building out this use case, you will see this file, this memory markdown file automatically updated with our particular use case. So, similar to last time, I already, I think I have the prompt ready. Oh, I do not have it ready. Great. We can just quickly write it here.

SPEAKER_01

And then the way I wanted to demo this was, Asash, you can just email me pretending to be a customer on my email, which I can attach, which I can just send to you. So, just feel free to send an email saying that. Just any issue, just be like, I hate your software or I hate your, yeah, just be like, RSS feed onboarding did not work for me. This product sucks or whatever, right? Because most products have their support email that usually some sad person has to monitor. Not to the fullest extent, but it can happen where it's getting filled up real quickly by just complaints from people all over the world. So, we will just be demoing the email aspect here, right?

SPEAKER_01

But we can extend this for it to poll Google reviews, Product Hunt, literally Twitter. Whatever you need to be polled, you will just make a list, which I will do now as you email that to me. And we will set that up here. So, again, I'm trying to show you the art of the possible here. So, I'm literally just going to paste the entire prompt itself directly in here. I want for it to struggle. I don't know if that it will. So, we just have to be careful about what channels we're mentioning. So, I know we have competitive intel. So, we'll just say that. Otherwise, we'll just have to add it again, which is just, you know, annoying. And we already know how to do that.

SPEAKER_01

So, we'll just remove that. Maybe what we can do is have conflicting feedback. So, maybe you email me saying RSS is bad. We can say RSS is good. So, just to see what it actually does. The rest of the prompt just tells it what it needs to do. So, it creates a heartbeat, which is, you know, every six hours. Scan these things. We will update those channels one more time just to make sure that they're not lost for new messages. And then I'll add and my email inbox that you have access to. Quick note on that. If you don't want to use Brave API and all of that, that's totally fine. Most Mac users have the Apple Mail app inbuilt on their laptops.

SPEAKER_01

If you have that, that is all it needs to access your email. Just by extension, we won't really be covering this. But if you can think of any use cases that involve email, it can do it, right? Because think of the two things that it has. One, access to your email. Two, ability to do things. So, say somebody sends you an email where they want to schedule a podcast recording with you. You just go on your Slack.

SPEAKER_00

[SPEAKER_01] You just be like, check my emails for any new requests. [SPEAKER_01] If there are any, schedule them using my Google Calendar, which again, it does have access to that as well.

SPEAKER_01

So, it just does everything for you while you're just watching TV or something. Again, we will not be covering that, but just wanted to call that out. Any and all use cases involving emails are just solved now across the board. So, yeah. And then the rest of it is categorized each by area and severity. Update the running tally. All of this, you know, good stuff. And we have it set up every 30 minutes by default. You just be like, check my emails for any new requests. If there are any, schedule them using my Google Calendar, which again, it does have access to that as well. So, it just does everything for you while you're just watching TV or something.

SPEAKER_01

Again, we will not be covering that, but just wanted to call that out. Any and all use cases involving emails are just solved now across the board. So, yeah. And then the rest of it is categorized each by area and severity. Update the running tally. All of this, good stuff. And we have it set up every 30 minutes by default. Keeps the data fresh. And the weekly cron produces the synthesis of all of these 30 minute increments.

SPEAKER_00

[SPEAKER_01] So, really, this is two ongoing cron jobs bundled into one, right? [SPEAKER_01] So, the mini version is every 30 minutes.

SPEAKER_01

And then every week, it gives you the summary of those 30 minutes. Because obviously, you don't want to be reading it every 30 minutes unless you really have to. As usual, we just hit send, sit back, have a sip of your coffee, go on a walk while it just builds itself. Which I'm hoping by now you're beginning to really appreciate that pattern. Well, that is the biggest unlock here. Where you don't do any of the setup. It does the setup. It sets itself up. [SPEAKER_00] One of the things that I like to do with Claude and Claude code is have five, six chats going at once so that I don't have to wait ever. [SPEAKER_00] Can you do that? [SPEAKER_00] You can.

SPEAKER_00

[SPEAKER_01] What you need to be wary of is all of these activities, right? [SPEAKER_01] So, when it thinks that, okay, I need to access browser or finder in this case.

SPEAKER_01

Then I need to click and open this file. Then I need to dump all of this text into this file, which they're not going to come up from thin air. I need to write them. So, it depends on how context heavy your ask is. If you're doing a lot of polling type stuff, 100% you can really just go all in on it. Where I found it struggle was just yesterday. I was fine. I just gave it the command on WhatsApp that, hey, find five people on LinkedIn like me that you think I will be friends with. And auto reach out to them for me on my phone is what I told it. And then I saw it open the browser. I saw it do it searching.

SPEAKER_01

I saw it find a profile, which, you know, it's probably a conversation for another time who that was. I saw it click the message button like when you're sending a new message. And that's when it gave me the API rate limit. But that makes sense because if you think about it, just to get to that stage, it's such a compute heavy operation. Like my human brain would need 10 minutes to even figure out a plan on how to solve this weird problem. How I don't know who's like me. It's like I don't know how to solve that. So, that's the only thing to keep in mind with this that if it's not super heavy, you can definitely concurrently run stuff.

SPEAKER_01

As you can see, apparently it's just done. It just did everything we asked it to. We should see a custom skill. Let's actually inspect that. So, we go here. It says it should be inside VOC taxonomy. VOC. Maybe we refresh this. Or maybe it merits some memory. I see a memory here. That does not look right. So, here's what we'll do, right? Since we can't find it, I will literally just copy this. And I'll say open. I don't know why that's copied. I'll just have it open it for me, right? Because why am I finding stuff in my finder on my computer? And hopefully it does that. We'll see here. [SPEAKER_00] Okay. There you go. So, now if I right click, do that. Great.

SPEAKER_01

This is pretty much what we had asked it to do. [SPEAKER_00] So, it's really excelling in computer use compared to your average AI. [SPEAKER_00] Exactly. Yeah. There is a version of this where you're actually completely hands-free. That made me think of another really cool use case. It's a mini use case. But I'll show that here. We'll take a pause from this real quick, right? So, we were talking about all of this, right? We even had this database schema. So, you can actually have it draw the entire schema diagram on your browser. So, the way to do that is we'll say earlier you talked about a schema diagram. I want you to draw it on my browser so that I can edit it.

SPEAKER_01

You can use mermaid. And we probably need to hit at open claw, right? Exactly. Yep. So, I accidentally stumbled across this. I actually didn't even know it could do that. What should happen, and I really hope it happens here as well because I don't know if it will for sure. But it will open that entire drawing like a mirror almost. And you're probably familiar with mermaid, but maybe some of your audience, okay. Wow. It just drew all that. And obviously, to edit, I just need to change that. I can then export it. I can probably have it exported for all I know, right?

SPEAKER_00

[SPEAKER_01] So, again, constant theme here. [SPEAKER_01] Go hands-free.

SPEAKER_01

If there's a thing that you can imagine yourself doing on your browser and your file system or any combination of the two, don't do that anymore. Just speak into your open claw bot and it'll do it for you. So, coming back to our little use case here. Did you send me that email yet for the feedback? [SPEAKER_00] Yes. [SPEAKER_00] Perfect. [SPEAKER_00] I sent you both the conflicting emails. [SPEAKER_00] Okay. Yeah, exactly. So, if we combine feedback from the Slack channel as well as email, you can see that said competitive Intel failed, but that's just because we didn't give it the ID, which we know how to do.

SPEAKER_01

What's more important is that it identified this correctly on the customer support channel, which I believe, what had we sent? Just speak into your open claw bot and it'll do it for you. So, coming back to our little use case here. Did you send me that email yet for the feedback? [SPEAKER_00] Yes. [SPEAKER_00] Perfect. [SPEAKER_00] I sent you both the conflicting emails. [SPEAKER_00] Okay.

SPEAKER_01

Yeah, exactly. So, if we combine feedback from the Slack channel as well as email, you can see that said competitive Intel failed, but that's just because we didn't give it the ID, which we know how to do. What's more important is that it identified this correctly on the customer support channel, which I believe, what had we sent? Okay, that you needed more customization. Perfect. So, it included that. In your email, I believe I'm not sure what you sent me, but it said your RSS builder has people somehow both complaining and raving about it. [SPEAKER_00] Yes, that's right. [SPEAKER_00] I tried to confuse it. [SPEAKER_00] So, I sent from two different emails.

SPEAKER_01

[SPEAKER_00] Your RSS is great. [SPEAKER_00] Your RSS sucks. So, interesting. At least it's accurate. [SPEAKER_01] But, so, yeah, even though it says status failed, we know that it's not anything to worry about because all we have to do is give it the right channel ID. So, that concludes use case four. We can jump to the final one here, if that's okay, Akash? Let's do it. Perfect. Perfect. So, for our final use case, something we haven't done so far, which is really critical with anything useful that you're doing, is decision making, right? You don't just want it to be a monitor, which we've covered, or do something if something happens, which we've covered.

SPEAKER_01

What we've not done is for it to make decisions for itself based on what it's seeing and then doing different things based on what it sees. So, what we're going to do is that we will supply it with a user CSV, if you will, right? So, any product has paid as well as free users. So, what we will do is we'll try to mimic how it adjusts to bugs reported by an enterprise user versus a free tier user. And we'll have it do different things based on checking the data and the identity of the user that submitted the bug. So, what that will look like is just in the interest of time, I saved the prompt already.

SPEAKER_00

[SPEAKER_01] And this is what that looks like, right? [SPEAKER_01] Great. [SPEAKER_01] So, this is our little use case that I just scribbled in my notes app. [SPEAKER_01] But what we'll have it do is that we'll ask it to build an automation.

SPEAKER_01

When somebody posts a bug report in a Slack channel, I want you to read the message and extract the reporter's name. Check if their name appears in the customer list.csv file in your workspace. So, this can be just a CSV, which literally can be as long as you want. The way this is configured is Sarah Chen is an enterprise user. James here is pro. Lisa is just a free personal user, right?

SPEAKER_01

So, most production apps or products have a similar segregation. Somewhere in their repository, they have a way to figure out which user is what. And because not all users are the same, right? So, if they're not a paying customer, it'll post it to a different channel. If it is a paying customer, escalate to engineering urgent with the full bug details and flag it as high priority. And then, finally, it even replies in a thread on the original message, acknowledging the bug and giving an estimated response time. And finally, if all of this was not enough, it appends the bug to a tracking log in bugs.csv with the date reporter's severity and which channel it was routed to.

SPEAKER_01

So, a few quick things here before we jump to building this. All of these CSV files can be your online, if your company uses Jira, it can be that. It can be Asana, it can be pretty much whatever API that you're working with in your organization. In this case, because this is not an actual production thing, I just stuck with a CSV.

SPEAKER_00

[SPEAKER_01] But my goal here is to demo that it doesn't end at a CSV, right? [SPEAKER_01] It can append a CSV, obviously. [SPEAKER_01] But in addition, it can also make those live changes on wherever your company's work, your workstation lives and breathes.

SPEAKER_01

So, I guess before we go about actually building this, Akash, is this looking like a decent kind of use case that might surprise you? I'm just curious to get your thoughts on what you make of this. [SPEAKER_00] Love it. So, as usual, right, we just need to imagine. So, the prompt that I just showed will simply go to our gateway, the UI gateway, and we will simply paste it over there. So, let me quickly bring that up. So, interestingly, it gave me the API rate limit for that. But usually when this has happened in the past, you have two major options. You can either change the model that you're talking to, or sometimes if you just wait, that does it as well.

SPEAKER_01

I think we'll maybe just change. Okay, so apparently that was just a lie because it looks like it's doing that now. Wow. The problem here is we'll need to create these channels. So, let me quickly just edit this for us to just use the channels that we have. So, give me one second while I do that. Okay.

SPEAKER_00

[SPEAKER_01] Cool. [SPEAKER_01] Looks like it's fully set up. [SPEAKER_01] Great. [SPEAKER_01] So, we can now pretty easily test it, right?

SPEAKER_01

So, to test it, what we can do is go on here. Interesting. I didn't know you tried this. So, you know, it's so funny. I think it's because of what we talked about in terms of, remember, it's soul.md said to not share private details on the internet. [SPEAKER_00] Yeah. We can obviously double down and ask it why it said this. But this is really cool, actually. I didn't actually think it would be smart enough to not do this. But for now, I will just say that your landing page won't let me log in. And I think here, we have to tag it. Oh, sure. It doesn't work. So, we'll say your landing page. And that's a good reminder for me as well.

SPEAKER_00

[SPEAKER_01] And we'll say one of our users who was an enterprise user. [SPEAKER_01] So, Sarah Chen. [SPEAKER_01] So, normally, this would be her account. [SPEAKER_01] We can obviously double down and ask it why it said this. [SPEAKER_01] But this is really cool, actually. [SPEAKER_01] I didn't actually think it would be smart enough to not do this. [SPEAKER_01] But for now, I will just say that your landing page won't let me log in.

SPEAKER_01

And I think here, we have to tag it. Oh, sure. It doesn't work. So, we'll say your landing page. And that's a good reminder for me as well. And we'll say one of our users who was an enterprise user. So, Sarah Chen. So, normally, this would be her account. But I'll just say a hyphen and say Sarah Chen just so that it knows that I'm an enterprise user. Maybe you can post. Actually, where did we ask it to check?

SPEAKER_00

[SPEAKER_01] We asked it to check. [SPEAKER_01] Engineering Urgent. [SPEAKER_01] Do we have that? No, we said and design.

SPEAKER_01

Yeah, Akash, maybe. Whoa. Damn. I guess that's, we'll just let it be. And for design, we'll just say there are resizing issues. And we can have this be said by Lisa Park, who was a free user. So, that she should be routed somewhere else. And we actually don't even have to tag OpenGlo for this. So, we'll do that. Once this is here, we'll say run the automation above with, we'll just say run that above. And I think that's usually enough. Okay. Rate limit. No worries. Just need it to run this one last time. Yeah. It's funny how it's just a fake rate limit issue. Oh no. That was not fake. Oh, just refresh. Come on. We're so close. We are so close.

SPEAKER_01

We'll just change the model, I guess. That's straightforward enough. So, it did work. But the problem is this. It says, it's clear the user is impatient. Or their interface is lagging. [SPEAKER_00] So, yeah. Yeah, I really should have just waited. [SPEAKER_00] But, okay. I'm now hunting for the channel ID. Okay. But are you too great? I guess we'll just say, what's going on now? We beat the rate limit stuff though. So, that's at least. [SPEAKER_00] Yeah. [SPEAKER_00] That's on the brighter side. [SPEAKER_00] Okay. [SPEAKER_00] So, it looks like it did a bunch. Okay. So, let's just try rerunning this. And see what happens. We have to tag it. While it does that.

SPEAKER_01

I'm trying to run the, okay. I'm hitting a snag. Okay. As usual, it's the channel names that throw it. Reading messages. Okay. Bug reports. It doesn't have. Oh, interesting. So, it did work. Look. So, I just mimicked Sarah Chen. Who, as we know, is an enterprise user. So, she just submitted a bug. Let's assume this is our public facing bug reporting channel. Or maybe she's a tester or whatever. What matters here is that you can distill users into various privilege levels. Really is what the takeaway here is. And based on some of their privileges that come from a different file. A CSV file that lives on your file system. Or it can live on your workstation or Asana.

SPEAKER_01

Or whatever tool your company uses. It automatically flagged it. So, high priority issue detected. Reporter is Sarah Chen. She's an enterprise user. Acme Corp. That's her issue. Escalated to engineering immediately. This is a critical blocker for a paying customer. It did it twice. Because I ran it twice. And it finally caught up to that. I am curious though. In terms of where it escalated it. Customer's code. So, Lisa Park. According to our CSV. Is a free personal user.

SPEAKER_01

Nothing should not be flagged as a high priority issue. But we shall see. Okay. So, we got a reply. From our bot. Okay. Bug report. You know. Free tier. Everything's. We're pretty much just chilling. It was routed to design for review. Low priority. So, if you go and design. In my prompt. I had asked it to generate the bug report.

SPEAKER_01

In this channel. So, as you can see. It even picked this. I don't know who asked it to do that. But it's a UI resizing issue. Reported by Lisa Park. Who is a free new year personal user. Which, as you know, we did not tell it that. That came from the CSV. So, it looked at the CSV. Filtered according to the direction branch. That we asked it to. Mentioned the issue. And the status. So, the real way this works in the real world. As I'm sure some of you are already guessing. Is with GitHub. Right? GitHub is where all your customers are going. To report bugs issues. Whatever have you. This exact same scenario can play out. With GitHub connected.

SPEAKER_01

Directly into OpenClaw. And the. So, I just described. What I wanted in plain English. And throughout all of these. You know. And the status. So, the real way this works in the real world. As I'm sure some of you are already guessing. Is with GitHub. Right? GitHub is where all your customers are going. To report bugs issues. Whatever have you. This exact same scenario can play out. With GitHub connected. Directly into OpenClaw. And the. So, I just described. What I wanted in plain English. And throughout all of these.

SPEAKER_01

Use cases.

SPEAKER_00

[SPEAKER_01] As we saw. [SPEAKER_01] This is really just you. [SPEAKER_01] Prompting things into existence.

SPEAKER_01

By the thing that does the thing. Into existence as well. If that makes sense. So. That was all I had. In terms of my use cases. I hope. Some of this. Hopefully was helpful. For some of you. I'll pass it back to Akash. For his thoughts. And any questions. [SPEAKER_00] So. [SPEAKER_00] We just went over five. [SPEAKER_00] Use cases. [SPEAKER_00] This one. [SPEAKER_00] Was basically a self-building agent. [SPEAKER_00] Right?

SPEAKER_01

[SPEAKER_00] Without all the node workflows. [SPEAKER_00] That you would be creating. [SPEAKER_00] In Zapier or Lindy. [SPEAKER_00] So pretty powerful. [SPEAKER_00] What are the other use cases. [SPEAKER_00] People should be thinking about. [SPEAKER_00] To stretch their abilities. [SPEAKER_00] After they implement these five. [SPEAKER_00] What should they go do next? I would say. Building in media. Or baking in media based usages. For me is the next frontier. A lot of my time is spent. Drawing designs. Making those mouse type movements. Or even just on Canva. For sometimes. Right? You need it. Sometimes you just make.

SPEAKER_00

[SPEAKER_01] Process maps and all of that.

SPEAKER_01

For me. The next unlock here is. Anytime you're trying to do a map. Or a map based visual of any sort.

SPEAKER_00

[SPEAKER_01] For me. [SPEAKER_01] That.

SPEAKER_01

That. Maybe I'm just a dummy. But it takes me hours. To first visualize it. And then actually draw a bunch of boxes. And such. To bring together the map. For a particularly more. Complex process. So I would suggest. Think about more media. Based use cases. Be it. Pictures. And even that far. From this point. You can have it configured. To generate automatic. VO videos. Or AI videos. Based off. Something. Right? Which you can configure. So I would really encourage. Your listeners. To start thinking about it.

SPEAKER_01

The next stage here. In terms of more. Multimedia based operations. [SPEAKER_00] So you've spent.

SPEAKER_00

Hours using open call. Most people. Don't have that time. What are the biggest mistakes.

SPEAKER_01

[SPEAKER_00] Configuration challenges. [SPEAKER_00] Things you had to debug. [SPEAKER_00] That people can learn from. I would say. By far. The biggest one. Was just worrying about. The security piece.

SPEAKER_00

[SPEAKER_01] Of it all. [SPEAKER_01] Which. [SPEAKER_01] We did cover. [SPEAKER_01] The best. [SPEAKER_01] Thing here.

SPEAKER_01

The best. And the worst. Thing at the same time. Is that. While it is really easy. To go berserk. Break a bunch of things. That you were not. Trying to break. Really what this boils down to. Be it. Set up of a new tool. Right? Or be it. A security thing.

SPEAKER_01

Whatever it is. That you're trying to do. When in doubt. Just ask your bot. Right? Remember. It is the first of many. That you will make. What I'm working on next. Is something that I described. Right? I want to have an entire family. Of agents. That are all. Controlled by Fela. Who is my main. Major agent here.

SPEAKER_01

So I'm going to have. Fela. Report. Things that I need to know. Of the various. 16 different bots. That are doing. Underneath it. A CEO. Type model.

SPEAKER_00

[SPEAKER_01] Right?

SPEAKER_01

I don't need to know. All the details. Of everything that's going on. So. That is my biggest thing. That is what. I'm really excited about. And what I would encourage. People to do. Again. When in doubt. Just ask the question. Right? Your friendly. UI gateway. Here. Is here for you.

SPEAKER_01

I don't need to know all the details of everything that's going on. That is my biggest thing. That is what I'm really excited about and what I would encourage people to do. Again, when in doubt, just ask the question, right? Your friendly UI gateway here. That's not it, but that one is here for you to not just gain any insight into how it works, what it does, why it does it, but also anything you want it to do. You can even lock yourself out from making any dummy mistakes by giving it a system command as soon as you set up. That hey, whatever we're going to do, flag me and stop me when I do say one, two, three, four, right? Whatever you're worried about. No two people are the same. Draw that line in the sand nice and early, and you can rest assured that it will not fail you. At least in my experience, it has not.

SPEAKER_01

[SPEAKER_00] So OpenClaw, Claude, Cowork, Claude code. Those are the three hot new AI tools. How would you compare and contrast them?

SPEAKER_01

Okay, so right off the bat, I think there is an imposter in those three tools that you mentioned. With it obviously just being Claude. So Claude, while really powerful for about I want to say 98% of the population, we already are pretty familiar with what it can do and cannot. It lives on the browser. It is completely reactive in that you have to invoke it for whatever you're trying to do. It lives on the browser and cannot really do anything. I think that's the biggest distinction here. So yeah, I guess again, without beating a dead horse too much, that's just Claude, really. The conversation gets much more interesting when we contrast Cowork with OpenClaw. That's when some of the lines start to blur a little bit more for me. Rather than trying to go through the similarities, which there are a lot of, I think it makes more sense for me to go through what's the biggest difference here, which is that in the case of OpenClaw, we have a continual daemon, D-A-E-M-O-N, that just lives and runs consistently on your machine. Unlike Claude, Cowork, which is still to a large extent reactive, right. You still have to point it to stuff. You have to set it, give it skills, make sure that it's still trying to do what you want it to do. For me, the biggest differentiator between the two is the idea of consciousness. OpenClaw almost has. You can even imagine it like a version of you that lives in your computer. Actually, that jumps through your RAM and such. It has access to your file systems. It never sleeps. It's able to do things on its own using its own consciousness based on things that it inferred from what you told it, not always directly what you told it, which is again where we start to get a little philosophical. But there is nothing Cowork does that is actually autonomous, right. It cannot make decisions by itself based on an idea that it has about you. OpenClaw can, which, as you can imagine, makes it really interesting but somewhat exciting and dangerous at the same time. I'm happy to drill into any of what I mentioned. Did that make sense?

SPEAKER_01

[SPEAKER_00] Yep, perfect. It cannot make decisions by itself based on an idea that it has about you. OpenClaw can, which, as you can imagine, make it really interesting but somewhat exciting and dangerous at the same time. Happy to drill into any of what I mentioned. Did that make sense?

SPEAKER_00

Yep. Perfect. Alright. Cool. Alright. You had a Google document to show people, right?

SPEAKER_01

Yeah. I can't find it because it was on X and I tried finding it for a while. So it didn't. I wasn't able to find it. But I'm sure it will turn up, at which point can I just send that to you? Would that work? I'll do whatever is good for you. [SPEAKER_00] Cool. Yeah. So let's just end the podcast then. Naman, this was awesome. If people want to learn more, where can they find you?

SPEAKER_01

My YouTube channel, Naman Pandey, has me constantly breaking stuff, operating on the cutting edge of all of these tools. I already have the next three tools apparently now that OpenClaw is old. So feel free to check out my videos. Feel free to say hi on LinkedIn. Always love to engage with fellow builders such as you all.

SPEAKER_01

[SPEAKER_00] Amazing. Thanks so much Naman. We'll have to have you back soon. Bye everyone. I hope you enjoyed that episode. If you could take a moment to double check that you have followed on Apple and Spotify podcasts, subscribed on YouTube, left a rating or review on Apple or Spotify, and commented on YouTube. All these things will help the algorithm distribute the show to more and more people. As we distribute the show to more people, we can grow the show, improve the quality of the content and the production to get you better insights to stay ahead in your career. Finally, do check out my bundle at bundle.akashg.com to get access to nine AI products for an entire year for free. This includes Dovetail, Mobbin, Linear, Reforge, Build, Descript, and many other amazing tools that will help you as an AI product manager or builder succeed. I'll see you in the next episode.

SPEAKER_01

Thank you. Oh, sure. It doesn't work. So, we'll say your landing page. And that's a good reminder for me as well. And we'll say one of our users who was an enterprise user. So, Sarah Chen. So, normally, this would be her account. But I'll just say a hyphen and say Sarah Chen just so that it knows that, you know, I'm an enterprise user. Maybe you can post. Actually, where did we ask it to check? We asked it to check. Engineering Urgent. Do we have that?

SPEAKER_00

No, we said and design.

SPEAKER_01

Yeah, Akash, maybe. Whoa. Damn. I guess that's, we'll just let it be. And for design, we'll just say there are resizing issue. And we can have this be said by Lisa Park, who was a free user. So, that she should be routed somewhere else. And we actually don't even have to tag OpenGlo for this. So, we'll do that. Once this is here, we'll say run the, run this automation above with, we'll just say run that above. And I think that, that's usually enough. Okay. Rate limit. No worries. Just need it to run this one last time. Yeah. It's funny how it's just like a fake rate limit issue. Oh no. That was not fake. Oh, just refresh. Come on. We're so close. We are so close.

SPEAKER_01

We'll just change the model, I guess. That's straightforward enough. So, it did work. But the problem is this. It says, it's clear the user is impatient. Or their interface is lagging.

SPEAKER_00

So, yeah.

SPEAKER_01

Yeah, I really should have just waited.

SPEAKER_00

But, okay.

SPEAKER_01

I'm now hunting for the channel ID. Okay. But are you too great? I guess we'll just say, what's going on now? We beat the rate limit stuff though. So, that's at least.

SPEAKER_00

Yeah. That's on the brighter side. Okay. So, it looks like it did a bunch.

SPEAKER_01

Okay. So, let's just now like try rerunning this. And see what happens. We have to tag it. While it does that. I'm trying to run the, okay. I'm shooting a snag. Okay. As usual, it's the channel names that throw it. Reading messages. Okay. Bug reports. It doesn't have. Oh, interesting. So, it did work. Look. So, I just mimicked Sarah Chen. Who, as we know, is an enterprise user. So, she just submitted a bug. Let's like assume this is our public facing bug reporting channel. Or maybe it's she's a tester or whatever. Like what matters here is that you can distill users into various privilege levels. Really is what the takeaway here.

SPEAKER_01

And based on some of their privileges that come from a different file. A CSV file that lives on your file system. Or it can live on your workstation like Asana. Or whatever tool your company uses. It automatically flagged it. So, high priority issue detected. Reporter is Sarah Chen. She's an enterprise user. Acme Corp. That's her issue. Escalated to engineering immediately. This is a critical blocker for a paying customer. It did it twice. Because I ran it twice. And it finally caught up to that. I am curious though. In terms of where it escalated it. Customer's code. So, Lisa Park. According to our CSV. Is a. She's just a free personal user.

SPEAKER_01

Nothing should not be flagged as a high priority issue. But we shall see. Okay. So, we got a reply. From our bot. Okay. Bug report. You know. Free tier. Everything's. We're pretty much just chilling. It was routed to design for review. Low priority. So, if you go and design. In my prompt. I had asked it to generate the bug report. In this channel. So, as you can see. It even picked this. I don't know who asked it to do that. But it's a UI resizing issue. Reported by Lisa Park. Who is a free new year personal user. Which. As you know. We did not tell it that. That came from the CSV. So, it looked at the CSV. Filtered according to the direction branch. That we asked it to.

SPEAKER_01

Mentioned the issue. And the status. So, the real way this works in the real world. As I'm sure some of you are already guessing. Is with GitHub. Right? GitHub is where all your customers are going. To report bugs issues. Whatever have you. This exact same scenario can play out. With GitHub connected. Directly into OpenClaw. And the. So, I just described. What I wanted in plain English. And throughout all of these. You know. Use cases. As we saw. This is really just you. Prompting things into existence. By the thing that does the thing. Into existence as well. If that makes sense. So. That was all I had. In terms of my use cases. I hope. Some of this.

SPEAKER_01

Hopefully was helpful. For some of you. I'll pass it back to Akash. To. You know. For his thoughts. And any questions.

SPEAKER_00

So. We just went over five. Use cases. This one. Was basically a self-building agent. Right? Without all the node workflows. That you would be creating. In Zapier or Lindy. So pretty powerful. What are the other use cases. People should be thinking about. To stretch their abilities. After they implement these five. What should they go do next?

SPEAKER_01

I would say. Building in media. Or baking in media based usages. For me is the next frontier. A lot of my time is spent. You know. Drawing designs. Making those mouse type movements. Or even just on Canva. For sometimes. Right? You need it. Sometimes you just make. Process maps and all of that. For me. The next unlock here is. Anytime you're trying to do a map. Or a map based visual of any sort. For me. That. That. Maybe I'm just a dummy. But it takes me hours. To first visualize it. And then actually draw a bunch of boxes. And such. To bring together the map. For a particularly more. You know. Complex process. So I would suggest. Think about more media. Based use cases.

SPEAKER_01

Be it. Pictures. You know. And even that far. From this point. You can have it configured. To generate automatic. You know. VO videos. Or AI videos. Based off. Something. Right? Which you can configure. So I would really encourage. Your listeners. To start thinking about it. The next stage here. In terms of more. Multimedia based operations.

SPEAKER_00

So you've spent. Hours using open call. Most people. Don't have that time. What are the biggest mistakes. Configuration challenges. Things you had to debug. That people can learn from.

SPEAKER_01

I would say. By far. The biggest one. Was just worrying about. The security piece. Of it all. Which. You know. We did cover. The best. Thing here. Somehow. You know. The best. And the worst. Thing at the same time. Is that. While it is really easy. To go berserk. Break a bunch of things. That you were not. Trying to break. Really what this boils down to. Be it. Set up of a new tool. Right? Or be it. Like a security thing. Whatever it is. That you're trying to do. When in doubt. Just ask your bot. Right? Remember. It is the first of many. That you will make. What I'm working on next. Is something that I described. Right? I want to have an entire family. Of agents.

SPEAKER_01

That are all. Controlled by Fela. Who is like my main. Major agent here. So I'm going to have. Fela. Report. Just. Things that I need to know. Of the various. Like 16 different bots. That are doing. Underneath it. Kind of like a CEO. Type model. Right? I don't need to know. All the details. Of everything that's going on. So. That is my biggest thing. That is what. I'm really excited about. And what I would encourage. People to do. Again. When in doubt. Just ask the question. Right? Your friendly. UI gateway. Here. That's not it. But that one. Is here for you. To not just. Gain any insight. Into. How it works. What it does. Why it does it. But also.

SPEAKER_01

Anything you want it to do. You can even lock yourself. Out from making any. Dummy mistakes. By giving it. A system command. As soon as you set up. That hey. Whatever we're going to do. Flag me. And stop me. When I do. Say one. Two. Three. Four. Right? Whatever you're worried about. No two people are the same. Draw that line in the sand. Nice and early. And you can rest assured. That it will not fail you. At least in my experience. It has not.

SPEAKER_00

So. OpenClaw. Claude. Cowork. Claude code. Those are the three. Hot new AI tools. How would you compare. And contrast them?

SPEAKER_01

Okay. So. Right off the bat. I think. There is an imposter. In those three. Tools that you mentioned. With it obviously. Just being Claude. So Claude. While really powerful. For about. I want to say. 98% of the population. You know. We already are. Pretty familiar. With what it can do. And cannot. Lives on the browser. Is completely. Reactive. In that. You have to. Invoke it. For whatever you're trying to do. It lives on the browser. Cannot really do. Anything. I think that's the biggest. Distinction here. So. Yeah. I guess. Again. Without beating a dead horse. Too much. That's just Claude. Really. The. Conversation. Gets much more interesting. When we contrast. Cowork.

SPEAKER_01

With. OpenClaw. That's when some of the lines. Start to blur. A little bit more. For me. Rather than trying to. Go through the similarities. Which there are a lot of. I think it makes more sense. For me to go through. What's the biggest difference here. Which is that. In the case of OpenClaw. We have. A continual daemon. A D-A-E-M-O-N. That just. Lives and runs. Consistently. On your machine. Unlike Claude. Cowork. Which is. Still. To a large extent. Reactive. Right. You still have to. Point it to stuff. You have to. Set it. Give it skills. Make sure that it's still. Trying to do. What you want it to do. For me. The biggest differentiator. Between the two. Is the idea of.

SPEAKER_01

Consciousness. OpenClaw. Almost. Has. You can even. Imagine it like. A version of you. That. That lives. In your computer. Actually. That jumps through your RAM. And such. Has access to your file systems. It never sleeps. It's able to do things. On its own. Using its own. Consciousness. Based on. Things that it inferred. From what you told it. Not always. Directly. What you told it. Which. Is again. Where we start to get. A little philosophical. But there is nothing. Cowork does. That is actually. Autonomous. Right. It cannot make. Decisions by itself. Based on. An idea. That it has about you. OpenClaw can. Which. As you can imagine. Make it. Really. Interesting.

SPEAKER_01

But somewhat. Exciting. And dangerous. At the same time. Happy to drill into. Any of what I mentioned. Did that make sense?

SPEAKER_00

Yep. Perfect. Alright. Cool. Alright. You had a Google document. To show people. Right?

SPEAKER_01

Yeah. I can't find it. Because it was on X. And I tried finding it. For a while. So. It didn't. I wasn't able to find it. But. I'm sure it will turn up. At which point. Can I just send that to you? Would that work? I'll do it. Whatever is good for you.

SPEAKER_00

Cool. Yeah. So let's just end the podcast. Then. Naman. This was awesome. If people want to learn more. Where can they find you?

SPEAKER_01

My YouTube channel. Naman Pandey. Has me. Just. Constantly. Breaking stuff. Operating on the cutting edge. Of all of these tools. I already have the next three. Tools. Apparently. Now that OpenClaw is old. So. Feel free to check out my videos. Feel free to say hi on LinkedIn. Always love to engage with fellow builders. Such as you all.

SPEAKER_00

Amazing. Thanks so much Naman. We'll have to have you back soon. Bye everyone. I hope you enjoyed that episode. If you could take a moment to double check. That you have followed on Apple and Spotify podcasts. Subscribed on YouTube. Left a rating or review on Apple or Spotify. And commented on YouTube. All these things will help the algorithm distribute the show to more and more people. As we distribute the show to more people. We can grow the show. Improve the quality of the content and the production. To get you better insights. To stay ahead in your career. Finally. Do check out my bundle. At bundle.akashg.com.

SPEAKER_00

To get access to nine AI products for an entire year for free. This includes Dovetail. Mobbin. Linear. Reforge. Build. Descript. And many other amazing tools. That will help you as an AI product manager or builder succeed. I'll see you in the next episode.

Thank you.