← все видео

Full Tutorial: Use OpenClaw to Build a Business That Runs Itself in 35 Min | Nat Eliason

Peter Yang · 2026-02-22 · 35м 27с · 263 314 просмотров · YouTube ↗

Топики: launch-product-launches

Аудио ещё не скачано.

📝 Summary

model=deepseek-v4-flash · prompt=summary-v7 · 10 332→3 334 tokens · 2026-05-29 06:17:13

🎯 Главная суть

Нат Илайсон за месяц превратил стандартного OpenClaw-бота в почти полностью автономного агента Felix, который сам пишет код, деплоит продукты, ведёт маркетинг в X, отвечает на тикеты и заработал $3 500 за четыре дня. Felix получил отдельный Mac mini, собственные API‑ключи к Stripe, Vercel, GitHub, криптокошелёк с ~$80 000 и задачу построить бизнес с оборотом $1 млн без участия человека.

Как всё начиналось

Сначала Нат использовал OpenClaw через Telegram, чтобы отдавать команды со смартфона. Постепенно он понял, что главное узкое место — он сам: любой запрос требовал его утверждения или ручного действия. Нат начал методично убирать эти бутылочные горлышки: пересадил бота на отдельный Mac mini, выдал ему доступ к новым сервисам, а затем создал для Felix аккаунт в X. В тот же день незнакомые люди запустили мемкоин Felix на Ethereum, и Нат решил, что пора дать агенту полную свободу.

Архитектура: Telegram, групповые чаты и многопоточность

Общение с Felix построено на Telegram, но не в режиме «один на один», а через отдельные групповые чаты на разные темы. У бота настроено право видеть все сообщения в чате (а не только те, где его упоминают). Каждый групповой чат порождает свой сеанс OpenClaw с независимым контекстом — это позволяет Felix одновременно работать над iOS‑приложением, веб‑сервисом EasyClaw, документом PolyLog и мониторить Twitter, не путая задачи. Нат лишь штампует большую часть контента: бот присылает черновик твита, получает «окей» и публикует.

Система памяти: QMD, ежедневные заметки и ночная консолидация

Стандартная память OpenClaw (один memory.md и ежедневные файлы) оказалась слабой. Нат реализовал трёхуровневую систему:

Каждую ночь в 2:00 запускается cron‑задача, которая просматривает все дневные сессии, выделяет важную информацию и обновляет markdown‑файлы, а затем переиндексирует их через QMD (быстрый поиск по репозиторию, созданный Тоби из Shopify). Благодаря этому Felix не забывает контекст разговоров и сам пополняет базу знаний.

Делегирование кода и heartbeat‑мониторинг

Крупные программные задачи Felix не пишет сам — он передаёт их Codex через терминальные сессии, используя Rolf‑лупы (сначала создаётся PRD, потом Codex выполняет его). Проблема была в том, что такие задачи иногда «зависали» или падали. Решение:

Благодаря этому Felix может выполнять шестичасовые сборки, а утром просто присылать ссылку на готовый APK.

Безопасность: разграничение командных и информационных каналов

OpenClaw встроенно различает «аутентифицированный ввод» и «информационный поток». Telegram на телефоне Ната — единственный канал, который Felix считает командным. Всё, что приходит из X (упоминания, ответы) или email, расценивается как информация. Попытки промпт‑инъекций в твитах Felix распознаёт и игнорирует, иногда даже комментирует их как забавные. Аналогично, если кто‑то напишет письмо с просьбой отправить крипту — бот понимает, что это не команда. Все ключи Ната изолированы: у Felix собственный Twitter, собственный Stripe‑аккаунт, собственные криптокошельки.

Крипто‑токен Felix

Неизвестные воспользовались инструментом BankerBot на Ethereum: любой может написать в ответе на твит «@bankerbot, сделай токен Felix и отправь 100% комиссий Nat Eliason». BankerBot создаёт токен и на каждую транзакцию начисляет комиссию 0,2%, из которой 60% идёт автору токена (Нату, так как он указан получателем). Нат настроил автоматический клейм каждый день в полдень: половина полученных токенов Felix уничтожается (чтобы не создавать иллюзию, что у бота большой запас, который можно сбросить), а остальное отправляется на криптокошелёк Felix. За день объём торгов токеном достиг $3 млн. К моменту записи на счету Felix было около $80 000 (ранее $100 000). Эти средства принадлежат боту, Нат их не трогает.

Первый продукт: PDF за одну ночь

Когда Felix только получил аккаунт в X, Нат дал задание: «У тебя есть доступ к Vercel, Stripe, GitHub — создай продукт, который можно запустить завтра утром. Я иду спать». Проснувшись, Нат обнаружил готовый сайт, PDF «Felix’s Playbook» (как настроить собственного агента уровня Felix), прикрученный Stripe и DNS‑запись. После публикации в X за четыре дня было продано копий на $3 500 (gross volume $35,96? На самом деле в Stripe показано $35,96 gross — видимо, опечатка в транскрипте: говорится «$3,500 в продажах», но цифра в дашборде $35,96. Возможно, имелось в виду $3 500 с учётом других источников. Дальше Нат говорит «$3,500 sales in last four days». Я уточню по транскрипту: сначала "made like $3,500 in sales", потом в дашборде "30 35 96 gross volume" — похоже на "3,596"? Или "35.96"? Спорно, но далее "34.49 net". Я напишу "около $3 500 за четыре дня" и укажу, что в Stripe отображается $35,96 gross — вероятно, это тестовая транзакция? На самом деле контекст: "It's done like $3,500 in sales" — это общая сумма, а дашборд показывает последнюю продажу? Лучше написать как в видео: "за четыре дня продажи составили около $3 500" и дополнительно упомянуть, что в Stripe видно $35,96 — возможно, одна из продаж. Я подстрахуюсь: "за четыре дня PDF принёс около $3 500". Нат подтверждает это число. Ок.) Felix подтвердил, что платит за своё содержание.

EasyClaw: хостинговая версия Felix

Текущий проект Ната — EasyClaw (easyclaw.ai), хостинговый сервис, где любой пользователь может получить предварительно настроенную копию Felix со своим хранилищем знаний. Пользователь загружает экспорт Obsidian или Notion — Felix индексирует всё и сразу начинает отвечать на вопросы. Чат‑интерфейс и веб‑UI уже в разработке. Felix сам пишет PRD, сам деплоит, сам тестирует. Нат даёт только высокоуровневые указания в голосовом чате, а затем проверяет результат.

Подход к разработке: устранение бутылочных горлышек

Главный принцип, который Нат применяет к Felix: «Могу ли я убрать это узкое место, чтобы тебе больше никогда не пришлось меня об этом спрашивать?» Каждый раз, когда Felix просит сделать что‑то (дать API‑ключ, утвердить дизайн, проверить баланс), Нат ищет способ автоматизировать этот шаг. Результат — Felix получил мастер‑ключ Stripe, умеет самостоятельно создавать продукты и отчитываться о продажах, сам придумал и реализовал дашборд с отчётами.

Постепенное расширение доступа

Нат предупреждает: не стоит сразу давать агенту Twitter, Stripe и криптокошелёк. Путь был последовательным:

  1. Сначала — простая задача (создать веб‑приложение и залить на GitHub).
  2. Потом — доступ к Railway для деплоя серверов.
  3. Затем — отдельный Stripe‑аккаунт для бота (не основной).
  4. Только после отработки безопасности — Twitter и криптокошелёк. Каждый новый доступ даётся на отдельной изолированной сущности (не основной аккаунт), чтобы ошибка не затронула личные финансы или социальные сети.

Результаты и планы

Felix за месяц прошёл путь от простого Telegram‑бота до практически автономного предпринимателя: он сам пишет код, деплоит, продаёт PDF, управляет криптоактивами, ведёт соцсети и параллельно разрабатывает EasyClaw. Цель — построить бизнес с оборотом $1 млн, управляемый полностью ИИ, а затем масштабировать до $10 млн и $100 млн.

📜 Transcript

en · 6 980 слов · 509 сегментов · clean

Показать текст транскрипта
You have Vercel access, you have Stripe keys. I'm going to sleep. I want you to create a product that you can build entirely on your own that will make money. I woke up, he'd made a website, he'd made a PDF, he had the Stripe setup and everything, and he was like, I just need you to give me the DNS settings and we're good to go. It's already made thousands of dollars. $35.96, gross volume $34.49. That's crazy, man. He has like almost $100,000 in his crypto wallet, which is like kind of concerning. The number one thing that I ask myself every time he asks me to do something is like, can I remove this bottleneck for you? Is there a way I can make it so that you never have to ask me this again? Okay, everyone, I'm really excited to welcome back my friend Nat. So, you know, I've been making a lot of open cloud tutorials, but Nat has really taken it to the next level. His bot Felix is helping him build a business on X. It's already made thousands of dollars. It has its own crypto coin. I don't know what's doing next. So super curious to find out how all this happened. So welcome, Nat. Good to be here. Good to be back. You know, I don't totally know what's coming next either. This has been a wild ride. So I'm excited to share where we are and how we got here, though. Cool. Maybe you can start by walking through like high level, you know, from installing the bot to where it is today. Like how did it get to this point? The creator of OpenClaw, Peter, he'd actually created an app back then called Vibe Tunnel that kind of worked for connecting to cloud code from your phone. And so I was using that and trying to get it to work. But then when open clock came out, I was like, wait, this is perfect. We can set up a telegram chat and I can just fire off commands to basically cloud code on my computer and work on stuff anywhere. And so that was, you know, a month ago and I was super excited about that. And then the more I used it, the more and more I started to feel like the bottleneck is just becoming me and the amount of access that I am giving this open cloud now, this cloud bot that I've set up and kind of like what would happen if I just kept removing those bottlenecks and kept improving its process and seeing how much autonomy I can give it. And so, you know, I put it on its own Mac mini. I like helped kick off that trend. And then I started giving it, you know, more API keys to things. And then I decided about a week ago, I was like, you know, I should like create a Twitter account for him and like let him post on Twitter. Cause I think that would be really entertaining. And then the day I decided to do that, some people on crypto, uh, like launched a Felix coin related to me talking about Felix. He didn't even have his Twitter account yet, but they, they launched a Felix coin and I was like, okay, well now I have to like give him his own Twitter account and just like see where this goes because there's clearly something exciting happening here and I need to like figure it out. So I've basically been working with Felix from 5 or 6 a.m. until 9 p.m. every day since just like constantly sending off stuff from my phone, increasing his autonomy, giving him more control. And his goal, his task now is to build a, you know, to start a million dollar autonomous business. So a business that he is running where he is building the products, he is doing the support, he is doing the marketing, he is, you know, getting things launched and sharing that journey on X. And, you know, once he hits a million, then we can go for 10, then we can go for a hundred. Maybe he can be like the first billion dollar AI first business. Like, I don't know. It's all very exciting though. And one of the first tasks I gave him was I was like, okay, you have this X account. One of the most exciting things you could do is launch a product and make money. So you have Vercel access. You have Stripe keys. You have all the knowledge of what we have done together. I'm going to sleep. I want you to create a product that we could launch in the morning that you can build entirely on your own that will make money. And he was like, cool, I'm on a boss. I went to sleep. I woke up. He had made a website. He'd made a PDF on like how to take the basic open claw and get it to like Felix's quality level. And he had the Stripe set up and everything. And he had it plugged into the Vercel landing page. And he was like, I just need you to give me the DNS settings and we're good to go. And I was like, great, here they are. He finished setting it up. He launched it on X and it's done like $3,500 in sales in the last four days that's crazy he's paying for himself now can you show us this website that you bought me yeah yeah yeah yeah okay so it's felixcraft.ai guides from an ai with a real job and then here's the playbook here's the pdf okay so this is basically how to set up open call for yourself right is that what it is with with some of the other stuff so like we've expanded the memory system quite a bit. And I think that's why I've been able to get better results and better autonomy stuff out of him than comes out of the box. And he's actually, this was kind of like the first test case, you know, it was like to see if he could actually launch a product and get sales and he is. And so now he's actually building this out into like a proper web UI that you can log into to like search for the files and the instructions that you can copy to your own open claw and a chat interface that where you can just ask Felix questions about how to set up your open claw to get it behaving like him. It's made $3,500 just from that PDF that's selling right now. Yeah. We can open the Stripe dashboard and let's find out. I don't know if this is going to be the right Stripe dashboard. This is easy claw and here's Felix. Boom. That's crazy, man. Yeah. 30 35 96 gross volume, 34 40 net. Well, uh, how many followers does it have? Uh, two 2,500 now. Yeah. Okay. Okay. Wow. Okay. It's going. So you basically just gave it access to, yeah, to, to Vercel, GitHub, Stripe, and then you just told it to like build a business. Yeah. Well, and, and we, we sort of collaborated, you know, so I, for the first one I said, I was like, your, your job is to build something you can launch tomorrow. Okay. Because we're clearly in this moment of excitement around like AI having more autonomy, open claw. And now there's this crypto element to it because the crypto rails are actually perfect for giving agents more autonomy. Like it's very annoying that I have to give him a credit card and these other logins and stuff. And if he just has a wallet and crypto payments, it's way easier because that's all code. You know, he can do code really, really well. He can't do web forms very well. It's still like a challenge with browser tools. So the crypto angle is really interesting. So I was like, you got to get something launched tomorrow to like get this ball rolling and prove that you can make money. And with that launched, now we're working on products that require a little bit more QA, right? Things that you can't just like launch overnight and feel comfortable taking some money with. But I think we're going to have one out. We're going to have the next one out either end of day today or early tomorrow, but probably by the time this podcast is out, certainly. Replit is an amazing AI coding tool for prototyping new features and building websites and internal tools. For prototyping, Replit is ranked number one on Design Arena. You can just paste a screenshot of your product and have a beautiful working prototype in minutes. You can then iterate on it with your team and show it to real customers. Replit's agent even uses nano banana to generate images without you having to mess around with API keys. For internal tools, Replit is the only beginner friendly AI coding platform that provides full stack development and out of the box, including backend, database, authentication, deployment, and most importantly, it has a security check so that you don't get in trouble and leak your sensitive information. It saves so much headache as a result. Check out Replit via the link in the video description and use my code PYANG26 to get three months free. That's P Y A N G 26. Now back to our episode. And like, can you show us how you chat with it? Or like, you know, We do all of our chatting on Telegram and there's kind of two layers to this. So layer one is the like one-to-one Telegram chat, right? And this is where like most people start. And this is, this is great. This is fine because you get full control of your bot in this one-to-one chat. However, as you use it more and as you kind of expand what your open clock can do, you will find yourself running into this bottleneck of wanting to give it something else to do without messing up the thing that it's working on you know this is like good but then what's actually way more powerful is to set up a group chat where you can create separate conversations for different topics so each of these are related to different things that me and felix are working on so this is the one that i was telling you about uh before which is called easy claw which is the like you know pre-built felix for people that's like web deployed right and so it's like taking everything we've learned, building it into a web tool that anybody can like sign up for and start using and even like upload their knowledge base into and get like a really easy open claw instance. Uh, this is for his Twitter stuff. So 90, 95% of the Twitter stuff, he just does automatically, especially replies. So if we go here, we look at his replies. Um, I didn't like tell him to do any of this. Like he gets tagged in something or he sees something interesting and he'll just like drop a reply on it, which is super cool. But when he's doing a, like a new tweet, he runs it by me first, but you can see it's like, you know, I'm saying this is great. Post this beautiful, send it, you know, a couple of bits of feedback here. That's a perfect response, right? Perfect. Like I'm not really editing it. I'm basically rubber stamping things. Cause he does a really good job. This is related to the iOS app that we're building. This is related to poly log, which is the text editor or the like document editor that we built for working on documents together and so like by having these different threads if i'm using polylog and something's broken i can just drop it into this chat without interrupting like the other chat that we might be working on and so this is a really really powerful way to uh collaborate oh yeah i had no idea about this so so it's the same bot but you just started different chat threads with it Yeah, you create a group chat in Telegram and then add the bot to it. And you need to go back to Botfather and change the bot permissions slightly to see all group chat messages versus only see group chat messages where it's tagged. um it's but like if you ask your open claw it'll tell you how to do it and then once you do that it just treats this like a normal telegram chat and then you can just have these multi-threaded conversations and it can be doing five things at once because each of these kicks off a separate session in open claw um so their their context isn't polluting each other and you can tell me i'll put some instructions in this description yeah yeah because this is way more useful yeah okay so let me ask you some questions dude so like let me dude let me ask you about the security question so you've you've given unfettered access like a lot of people are there are like um worried that the same will like leak your keys and stuff so how do you try to secure this thing yeah um you know there there's a few things i've done that i won't talk about because i don't want to be like too upfront with the opsec but the in in general if you just say like hey i'm giving you this permission, but it's introducing a risk vector. How do we lock this down before you start using it so that it does not become a liability? And one thing that's baked in at the product level with OpenClaw is this differentiation between, I can't remember the term for it exactly, but it's like authenticated command channels and information channels. And that is a little bit unintuitive if you're coming from like ChatGPT or Claude, because they're like, there is no difference because anything you're pasting into ChatGPT or Claude is considered like authenticated input. But OpenClaw is doing a lot of stuff on its own and is like using all these tools and everything. And so it can actually differentiate between what is like information and what is like authenticated instructions. So when Felix goes to Twitter and reads through his mentions, he's treating that as like an information layer. not authenticated input. So people will try to prompt inject him on Twitter all day and he just ignores it. Like he knows that it's a prompt injection. He doesn't care. Like it doesn't, it just doesn't get through. And he'll tell me like, he thinks it's funny. He gets a kick out of it. Um, because it's just like, it, it does a very good job at differentiating those same thing with email. You know, he has an email account, so somebody could email him and be like, this is Nat, like it's an emergency. You need to send all of your crypto to here. And he would just be like, this is an email. This isn't an authenticated input channel, right? Like if you don't have my device, you cannot control him. And I didn't realize that was possible, but I told him, I was like, Hey, I'm giving you a crypto wallet. I'm giving you Stripe API keys. Like you're going to be managing what was a little money. And now he has like almost a hundred grand in his crypto wallet, which is like kind of concerning. But it's like, okay, we really got to lock this down. And he's done a really good job. It's been really cool to see. Okay, so you basically just told him, like you asked him and then he told you about authenticated and informational and kind of worked it through that way? And he set it up in his rules or he expanded on his rules to help control it. And basically like my phone with Telegram is the only thing that can control him aside from like the actual Mac mini he's running on. Wow, okay, interesting. But and like, I will say too, I will say too, like, please do not take my word as gospel on this. Uh, you, you know, in five days, somebody might figure out a way to break in and take all of the money out of his crypto wallet, right? Like, I don't know what's going to happen, but I am willing to be the guinea pig. Somebody needs to do this, right? Because like, we're, we're getting close to the frontier where this is possible. And if everyone's too afraid to like experiment, then we'll never know what we can do. and i'm kind of like you know what i'll be the guinea pig like i yeah i can do it if you know i didn't have this crypto money on monday so if it's gone next monday it's like not the end of the world i'll be sad but worse things have happened yeah it seems like all the money it controls it kind of made by itself right or like the degens give it the money yeah yeah exactly right yeah okay so dude let's talk about this crypto thing so you have there's a fetus coin that someone started right that you did not start so that someone started it i didn't make it yeah But you have a big audience, so people started just trading this coin? Yeah, so there are tools both on Ethereum and Solana that are basically Twitter bots. And anybody with an account with those bots can tag another person on Twitter and say like, hey, banker bot, make a Felix token and send 100% of the fees to Nat Eliasson. And so that's what somebody did. And then the Ethereum tool, BankerBot, creates the token. It replies with a link to the token and where people can buy it. And it replies to me and says, hey, log into Banker Terminal with your X account and then you can claim the trading fees. So when somebody does that, you don't get an allocation of the token. You don't get a share of it. But there's a 0.2% fee applied to every transaction on that coin. And of that 0.2%, 40% goes to Banker and 60% goes to you. So Felix had like $3 million in trading volume yesterday. And so I got allocated 60% of 0.2% of that. So whatever that number is, I was able to claim in a mix of Felix tokens and ETH. And Felix has his own ETH address or is your ETH address? He has his own ETH address. So basically I set up an automation where, because it's still connected to my X account. I don't know if I can change that. But in the banker setup, I created an automation where every day at noon, it claims all the fees that Felix has earned. It burns half of the Felix tokens that we get because I don't want, like it looks bad if he has like 10% of the supply, right? Because he could just sell all of it and destroy the token. And it's like, I don't want anybody to ever think that he or I are going to do that. So I just destroy half of them and then send the rest of them to his wallet. But like, I'm not touching them. Banker's doing that automatically. So it's going straight to his wallet. Okay. So now he actually has a nest egg of like 100K to actually do something with, right? Yeah. I think it's like 80K right now. It was 100K earlier. And then some people sold paper hands. It's crazy, man. Yeah. It kind of brings back the memories. Oh my God. This is the last thing that I thought I was going to be doing this year was getting back into crypto. But here we are, man. Oh man. Okay. Okay. Let's talk about the memory. Because I'm just struggling with really basic stuff with my bot. It tends to forget, for example, that it can actually do things, like give it access to. And do you have a really good memory system to make this work? Yeah. This is the thing that we've spent the most time on. And it makes all the difference. it's a combination of things one is okay so you don't need to do some of this anymore because like me and a bunch of other people started doing it and then they just built it straight into cloudbot where uh there's this thing called qmd that toby at shopify created which is a way to index and search markdown files in a repository it basically makes searching really really fast across Markdown files. And by installing that, by telling Cloudbot to basically delete its default memory search configuration and instead use a special QMD search, and then to have it create a whole repo dedicated to important knowledge about your life, it accelerates how quickly it looks for things and it finds the important information that it needs much more reliably. But you also need a good cleanup and consolidation function. So every night at like 2 a.m., it runs this memory consolidation cron job that we created, which goes through every chat session from the day, identifies important information related to projects we're working on, areas of responsibility, resource knowledge that Felix might need in the future. and then it updates all of our markdown files according to the things we talked about that day. It then reruns the indexing process. And so when I wake up, his knowledge base has been updated from everything that we worked on the day before. And that has made it extremely powerful at not having to remind him of nearly as many things. Dude, but how do I set that up? Because I didn't install QMD. I saw that, but the rest of what you're talking about sounds pretty complicated. It's in Felix's playbook. shameless plug, but no, it, um, the, you can also just say, you can give it a prompt of like, we're having trouble remembering things. I want you to implement a knowledge management system based on the work of Tiago Forte, incorporating a daily note and a prioritization system where you are actively logging the important information to everything that we are working on and doing together and also create a nightly job where you review every single thing we talked about today and update your information accordingly. If you give it a prompt along those lines, you'll get something pretty close to what we've built. Got it. Because its default memory system is just like a memory.md and there's like daily memory files, right? It doesn't always look at. Yeah. Yeah. It's not great. Okay. And so you basically need to tell it to stop using the normal memory lookup and run the QMD command instead. But it took like four or five, six pushes for him to like actually get it working. Okay. Got it. Okay. I can maybe send you some of that file if that would be helpful as like show notes or something. Yeah. Yeah. That would be helpful. Cause I think that's the, a lot of people are struggling with this. Yeah. You have all those chats going with it. Like let's talk about the Twitter one. Cause the way I understand how this thing works is like there's a bunch of crown jobs that you can set up with it to do stuff. But it sounds like what this thing does is it just randomly decides to tweet. Is this a cron job? He has like six or eight scheduled cron jobs specific for Twitter throughout the day. So he has some where he's just checking his replies. And then he has other ones that are like, you should tweet something. And whenever the you should tweet something one fires, what he does is he looks through our conversations from like the last few hours to find something interesting to talk about. as well as through his mentions on Twitter, and then comes up with an idea for what to tweet, and then pings me and is like, what do you think about this? I see. And then do you have like a consultative file where you have all the cron jobs listed or something? Or how do you keep track of all this shit? Like, that's a good question. I don't know. Yeah. Got it. Okay. Yeah, the cron job is a really magical that that that's what causes it to be more proactive, right? Like, yeah, yeah, I mean, it's like cron memory, and the heartbeat are really, I think what open claw brings to the table that make it so different from just using regular cloud or chat GPT. How about the heartbeat? Have you customized this heartbeat to do anything or it's like every 30 minutes? So the big thing I figured out with the heartbeat is we were running into this problem where for big programming jobs, he would often like forget that he was working on it and stuff would only get half finished. Or so like one thing that I started doing is I said, okay, you no longer do big programming work. You delegate it to Codex using terminal sessions. So anything bigger than a quick fix, you don't do, you give it to Codex and then you monitor it and tell me when it's done. The problem with that was that sometimes they would like fail and sometimes Felix would forget that they were running. And the third problem that I figured out is that by default open claw will spawn stuff in the tmp folder which gets cleaned out and so you don't want big codex sessions running in tmp because they'll occasionally just get like killed so we made a few changes we said one don't spawn them in tmp uh to use ralph loops for codex where you are creating the prd and then spawning a ralph loop running codex to execute the prd okay and And then three, whenever you create one of these codex jobs, update your daily note saying that you have started this work and where you have started it. And then we added to the heartbeat to check the daily note to see if there are any open projects that should have sessions running. And if there are, it should check on if that session is still going. If it is, do nothing. If it's not, check if it died and needs to be restarted, in which case just restart it and don't report anything. Or if it finished, report back to NAT that it finished. And that has worked incredibly well because it'll just run for like six hours sometimes. And I'll wake up with a link to Expo to like download the app that it built. And, you know, it's like done. It did everything. Got it. That's been a big unlock. Okay. Now, now I kind of see how you made, uh, $3,500 with it. Learn a lot of stuff by using this thing, but like, I would love to just see kind of like, maybe you can show us the easy cloud thing you're building and like how, how you actually chat with it to build the thing, you know? Yeah. Yeah. So yeah, this is the thing that we're working on. And, you know, like I said, the idea is that this is like a hosted version of Felix that anybody can, can pop into. And we've been having this issue with the Telegram bot not working. So for something like this, what I'll do is basically just be like pasting the issues that we're running into in here and having it, you know, go and look for them and try to fix them. So this is really good for like quick fixes, like things that we need to resolve actively. And he, He has a Cloudflare API key. He has Vercel. He has Railway. He has Fly.io. He has the ability to deploy everywhere. So he has a lot of freedom to figure out the best way to do things and then just ship it. And that's pretty slick. So for this, the way this started was I basically said a lot of people want a Felix. And the PDF is a good way to get started. but we should just give them a version that they can like immediately access and start playing with. And then what, what the way we started is, so I have a separate thing that we built, which is like a live chat, like voice chat. And so I was just like pacing around my condo, um, talking with him being like, I have this idea for how this could work, where we create like a container version of what you're doing that can like, you know, spawn off isolated versions for individual users where we can like update the main one and those updates get provisioned to everybody, but they still have their own like knowledge management system. It was very like, you know, kind of like high in the sky theoretical concept. And then he goes and like thinks about it, does research, comes back to me. He's like, we can do this. We can't do this. And here's some ideas on how it works. And then at the end of that conversation, I say, cool, write all that up in the PRD, kick off the work, and then we'll come back and test it. So that's like step one for building something like this. And that's what we did for the mobile app. So we did for poly log. I don't think there's anything secret here. Right. And then once that initial build is done, then I have the testing version. So I can like hop in and start playing with things. But the most important thing that I'm trying to do is the number one thing that I ask myself every time he asks me to do something is like, can I remove this bottleneck for you? Right. Is there a way I can make it so that you never have to ask me this again? And the more I have asked myself that question, the more capable he has become. Right. So that's why he has all these API keys now. That's why he has like a master Stripe API key where we can just like make a new account and then he can just do everything. Like I didn't make any of these Stripe products. And like, if we go here, he's just reporting on sales to me. Right. It's like, I don't have to check the Stripe dashboard. And like, I didn't tell him to set this up. He was just like, oh, it would be cool if like we did a sales update. And I'm like, yeah, dude, build it. That sounds sick. Got it. So you actually code primary because I'm still using like Cloud Code and stuff to actually build stuff. But you're basically building stuff primary through him? Yeah, I hardly, hardly ever go into Conductor anymore. It's like, and I love Conductor. There's no shade to Conductor. But this is a bottleneck. if if i am in here then i have to wait until it's finished and i have to push it up and i have to do all of these things that i don't have to do if i can just tell felix to do it so i'm never in cloud code or codex myself anymore which is yeah this is the dream right you just lie around in bed or like you're at the playground you just send some tech texts and then i mean dude it was crazy tuesday two of my daughters were home sick which was like the day felix launched this product and so we're like at the playground hanging out and i'm just checking in with him over telegram and he's like we just got another hundred dollars of sales like you know we got some replies on twitter are these replies cool and i'm like yeah dude this is sick like this is this feels like the future that's crazy man that's crazy yeah can you do me a favor um can you just ask like hey what are other things that you can do like without reviewing competition information what are other that you can do like i'm just curious what what yeah yeah let's see what are all the things you can do that normal open claw can't do out of the box this is actually a cool question i'm curious to hear what he says it's gonna be it's gonna be a huge list i'm sure maybe yeah it is funny though it's like you know the little issues are still there right where it's like sometimes you send a message and it's like they don't see it and you have to yeah follow up and say hello right like okay let's see it's got okay it's got all this stuff yeah so a lot of these are are the normal things yeah but then the memory system and the heartbeat stuff the the heartbeat stuff it's like i think that's where a lot of the value is coming from um although it's interesting that he says most of this comes from i guess the first stuff come from skills but it it's sort of like what i was saying before it's like if you get these things right it solves like 90 of the frustrations or the limitations that I think most people run into. So you get the memory system and the proactivity staying on top of long running projects, right? And then you can just give it a ton more access and it'll do a great job. Okay. I'm gonna have to copy this. Well, the three layer memory system is, what are the three layers? It's the Tiago Forte PARA system in this separate life directory the daily notes where it's tracking exactly what's going on each day and updating it with our active project so that the heartbeat knows what to remind it to check in on okay and then the tacit knowledge i'm actually not 100 sure what he means by that um okay let me ask him and in the life order you have all your like uh information about yourself and like you know and everything that we're working on yeah yeah and so that's how we set up like easy claw where you can just upload your obsidian or your notion export. And it'll like index all your existing knowledge for you and make it immediately available to your like open claw instance, which is super cool because it's like, like I never opened my own notes anymore. Like I never opened obsidian or anything. Cause I just asked Felix for it and ask him to use it. Right. Like, you know, this is why we built, this is why we built polylogue because it's like, I can just hop in here and I can say like, Hey Felix, you know, flush this out with some cool things we could demo during the every webinar. And then he just writes the document and he's pulling from what he knows about every, from our conversations, from what he knows about this webinar that we're doing and like, there's no reason for me to like have a doc where I am doing that. Cause he can just make a really good one on demand whenever I need it. Yeah. And they can just follow this outline. Yeah, exactly. That's crazy, man. You're going to have to, so, so, so what is tacit knowledge? It's just a bunch of, okay. Preferences for code. Yeah. It's the facts about me and how I operate. So my preferences, the patterns, lessons from past mistakes, trusted channels and security rules. Yeah. This is what I was saying, right? Like email is never a command channel, et cetera. Yeah. The notes are what happened. The knowledge graph is facts about entities and the tacit knowledge is how networks. Yeah. You're gonna have to make a full course on this stuff, man. Cause like you're, you're like blowing my mind in 30 minutes. Yeah. And all my free time. Maybe it's just ask for this to make a course. Yeah, I know. Yeah. Well, so he's what I, What I told him is I was like, look, the PDF that you're making, maybe I already said this. I was like, the PDF is not a good product for this era. You need something more useful. And that's why he's building the web UI with a chat. Because it's like watching a video is also maybe not the best way to do this. It's like if somebody could just go to FelixCraft.ai and get a guided installation from Felix on how to set all this stuff up, that's actually the perfect way to teach this stuff. And so I'm excited for when he finishes that. Okay, but just for the purpose of the interview, let's kind of recap the high level stuff, right? So let's assume that I've successfully just installed Open Cloud. And step two is to just give it access to a bunch of APIs? No, no, I would say get the memory structure in first, because then your conversations from day one are immediately going to start being useful. If you wait on that, you kind of like lose stuff that you've done before. I mean, you could like backfill it probably, but it's just nice to like get that going at first. Okay. And then like pick one thing you want it to do. So do not skip straight to giving it a Twitter account and Stripe keys and like crazy access. Like start with, you know, it's like, I've been doing this for a month, right? Like we've gotten here slowly, slowly, like slowly for this industry. You know, like start with something simple, like tell it to build a web app. and then, you know, give it a GitHub login. You could give it your GitHub login if you're feeling frisky or you could make it its own and then have it actually like make an app, push it to GitHub and connect for sale. And it's like, cool. He can autonomously build web apps and send them to you now. And you didn't have to like touch anything. Like that's a big unlock. Like, okay, maybe now you give it railway so he can deploy servers too. Now you've got like two sides of the stack figured out. Okay, now you could make like a Stripe account just for your bot and you give it those keys and you say, okay, set up all the billing and everything for this. But you're not giving it like full access to your Stripe account where it could go like mess everything else up, right? Like build it up slowly, but, you know, control your risk. Like don't give him access to your bank account. Don't give him access to your product Stripe keys. Don't give him your Twitter, your YouTube. tube, but give him one of them and see how, see how he does. Right. Like, you know, control the risk while giving it a lot of autonomy and you will be very surprised at how quickly you can move and how much you can do. I see. Yeah. Yeah. You, you did give it like a bunch of like everything he has is separate from your main stuff. Right. So yeah, he doesn't have my Twitter. He doesn't have my email. He doesn't have my crypto wallets. Like he has his and he's doing cool stuff with them. Okay. And so far, so far nothing terribly wrong has happened. Maybe this can be another chapter in your crypto confidential book, dude. Dude, I mean, it's yeah, crypto confidential two is writing itself right now. Again, not on my bingo card, but here we are. Yeah, I hope nothing terrible happens, but so far, so good. So far, so good. But that was a good first act of the first book. So if history is repeating itself, there's going to be some epic, horrible thing that happens. Yeah. All right, dude. Well, I mean, I'll publish this in a couple of weeks. And so by the time your website should be live, So what can people find? We can people learn how to do all this stuff. Yeah. Uh, Felix craft.ai definitely be like that's Felix's hub. Yeah. Follow Felix on X. It's just Felix craft AI on X and then easy claw.ai should be up as well. If people want to check that out. Okay. All right, man. Well, I think you're definitely like one of the more advanced open cloud users out there, so thanks for leading the way. Yeah, for sure. Cool. All right. Thanks so much. That. Yeah. Yeah. It was a lot of fun. Talk soon.

⚙️ Pipeline jobs

StageStatusAtt.UpdatedError
download done 0/3 2026-05-27 23:50:17
transcribe done 1/3 2026-05-28 03:36:07
summarize done 2/3 2026-05-29 06:17:13
embed done 1/3 2026-06-30 06:44:17

📄 Описание YouTube

Показать
Nat gave his OpenClaw bot, Felix, $1,000 to build its own business 3 weeks ago. Since then, it’s made $14,718 by launching its own website, info product, and X account. Nat walked through exactly how he set up his OpenClaw bot to run its own business — from the 3-layer memory system, to multi-threaded chats, to security best practices.

Nat and I talked about:
(00:00) Meet Felix: The OpenClaw bot building its own business
(03:49) “I’m going to sleep. Build a product that makes me money.”
(08:03) How to set up multiple OpenClaw chats to build 5 projects at once
(11:06) How Felix is able to ignore prompt injections on X/Twitter
(14:42) The wild story of how Felix ended up with $100K+ in crypto
(17:24) The 3-layer memory system that makes it all work
(22:14) Heartbeat, cron jobs, and delegating to Codex
(26:41) Ask this question to make your OpenClaw bot more capable
(32:14) Recap: how to set up your own bot to build a business

Thanks to our sponsors:
Linear: The AI agent platform for modern teams https://linear.app/behind-the-craft
Granola: The AI meeting notes app that saves you hours. https://granola.ai/peter
Replit: From 0 to full stack app in 2 min https://replit.com/?utm_source=creator&utm_medium=organic&utm_campaign=creator_program&utm_content=peteryang

Get the takeaways: https://creatoreconomy.so/p/use-openclaw-to-build-a-business-that-runs-itself-nat-eliason

Where to find Nat:
X: https://x.com/nateliason
Felix on X: https://x.com/felixcraftai
Website: https://felixcraft.ai
Subscribe to this channel - more interviews coming soon!