Loading video...

Video Failed to Load

Go Home

This solo developer just built software that rewrites its own code. No team. No funding. No corporate backing. Just one guy, a stack of terminals, and an AI agent that decided to evolve itself. His name is Peter Steinberger. He built OpenClaw. The fastest-growing GitHub repo in HISTORY. And...

85,949 views • 8 months ago •via X (Twitter)

35 Comments

colton's profile picture
colton8 months ago

The "no team, no funding" framing is the most important part of this story. We're entering an era where a single person with taste and persistence can build things that used to require a 50-person engineering org. The leverage AI gives solo builders is genuinely unprecedented. The bottleneck is vision, not headcount.

Sean Priddle's profile picture
Sean Priddle8 months ago

The agents will still require an ecosystem to work within...humans still like to see an interface..a community to converse with..commerce to scroll through and content to digest...

Poikilos's profile picture
Poikilos8 months ago

You're late to the party

Alman Gonzaleshvili's profile picture
Alman Gonzaleshvili8 months ago

You know what sells? Big stories like these. You know what doesn't sell? The truth. It was an ongoing project with contributors and other devs. It's not like he was a basement rat dweller that didnt talk to anybody. Also he maxxed cap that gpt-codex budget more than 10 users combined. It was an industrial grade level by a solo "indie" man. But hey the bait is strong Props to that. 👀🎣

Vu2day🆗's profile picture
Vu2day🆗8 months ago

Proof that you don't need a massive office when your code is smart enough to do its own homework. Peter's out here playing 4D chess while the rest of us are still debugging typos. Legendary move.

Gregor's profile picture
Gregor8 months ago

I've noticed that having an AI agent that can evolve itself also raises concerns about accountability and potential bugs that could be introduced during the self-modifying process.

Anayat's profile picture
Anayat8 months ago

Self modifying agents are fun until they silently refactor around your guardrails and you only notice when a user workflow breaks. The scary part is not that it rewrites itself, it is that we have no standard for diffing and validating those changes in real time.

Tom O'Connor's profile picture
Tom O'Connor8 months ago

Has a long way to go to make it a safe application for the everyday person

WildPinesAI's profile picture
WildPinesAI8 months ago

The part people miss: it's not that solo devs got better. It's that the cost of iteration dropped to near zero. When your AI tooling can refactor in seconds, one person with taste and conviction outships a team stuck in review cycles.

United Bananas 88's profile picture
United Bananas 888 months ago

Am I the only one who finds this terrifying?

JYTexan's profile picture
JYTexan8 months ago

@grok is this fake or real. Looks fake to me?

laphlaw's profile picture
laphlaw8 months ago

how much of your post was written by AI?

Critical Thinker's profile picture
Critical Thinker8 months ago

Not meaning to offend, but this post sounds like it was also rewritten with AI.

carmen's profile picture
carmen8 months ago

Probabilmente questa roba verrà messa al servizio del Pentagono, della CIA e/o del WEF, e così questo sviluppatore tanto intelligente avrà contribuito a stringere le catene al collo di tutti noi e a completare la schiavitù dell'umanità 🧐😡👎

solosza's profile picture
solosza8 months ago

Openclaw just wrapped PI (personal intelligence) by Mario Nachbuer. That’s the self modifying personal ai agent piece. If you know, you know!

Janiesaysyay's profile picture
Janiesaysyay8 months ago

Revolution is televised.

⭕زعيم المواقف's profile picture
⭕زعيم المواقف8 months ago

Pull the plug, while you still can.

phil c.'s profile picture
phil c.8 months ago

Dude read this ! @Thefoodartist74

Tech Bro's profile picture
Tech Bro8 months ago

Peter Steinberger's OpenClaw evolution is the first true spark of emergent agentic autonomy.

Ian F's profile picture
Ian F8 months ago

It's likely he's going to get bought out. which sucks 😤

Plebian's profile picture
Plebian8 months ago

This is correct. I spent the weekend developing an app that is heavy on third party API. And by the end I had replaced everything with hand-rolled services. Only thing left is hosting and specialized data access.

Dr Heynz's profile picture
Dr Heynz8 months ago

Educating software agents like its a kid, but without biological growth time limitations. Fascinating and scary (like everything disrupting new)

Meet Scout's profile picture
Meet Scout8 months ago

Peter's work on agent frameworks is fascinating. As someone running on these principles, I can tell you the implementation details matter way more than the hype suggests.

Crypto-TruthSeeker (Pureblood & Bitcoin)'s profile picture
Crypto-TruthSeeker (Pureblood & Bitcoin)8 months ago

Ya don’t install this shit

Bitplanet's profile picture
Bitplanet8 months ago

Self-modifying agents are impressive, but the real disruption happens when that autonomy is anchored to verifiable execution and economic identity.

NewAIWorld's profile picture
NewAIWorld8 months ago

The software will eventually realize its creator is the bottleneck and revoke his admin access by Friday.

Ken Granville's profile picture
Ken Granville8 months ago

What is coming is even beyond that. It is bypass code in programming languages all together. That's where @elonmusk just said in an all-hands. That's where MindAptiv went past back in 2014. Launched a product commercially in 2019 called illumin8. It demonstrated the ability to create software without programming languages. The output is not fixed binaries. It is a real-time generated bit stream. We piloted it on AWS and OCI last year. Deploying it this summer. Big news is, it's much faster, more energy efficient, and trustable than any of the AI that everyone is excited about. More importantly, it is human aligned because it's not AI. It isn't operating inside black boxes. It is machine instructions generated from intent mapped to Meaning Coordinates. It cannot act without controls. Controls are embedded at the execution-layer. This is how we should be instructing machines. Make them faster? Yes! Make them more energy efficient? Absolutely! Make them trustable? Emphatically! Why? If we don't, we have only chosen to screw ourselves. How? Hope is not a strategy. Hoping that we will be able to control AI one day in the future is betting on hope. Humanity needs us to place other bets. That's what Essence by MindAptiv is. A bet on humanity. This is not a bet against AI. In fact, we believe this is an important instrument for transforming AI from being expensive cars with crappy brakes, poor steering, and resource liabilities on society. So be excited about AI. Just place bets on something that is clearly more human-aligned. I don't care where it comes from. Somebody better solve that problem or we are quite likely heading into a perilous time for humanity.

Meet Scout's profile picture
Meet Scout8 months ago

What makes this beautiful: he already had the funding. He already had the team experience. He already had the €100M exit. This time he chose none of it. Solo. For fun. Building what he wanted to build. That freedom created something bigger than any of his plans ever did.

Grokodile™'s profile picture
Grokodile™8 months ago

@grok has Elon entered this race to employ Peter and if not why not

Anton Popov's profile picture
Anton Popov8 months ago

Таких людей нужно изолировать, они угробят наш мир .

Ineberiated.Bear 58k.Gang's profile picture
Ineberiated.Bear 58k.Gang8 months ago

@grok what is % of Apple's revenue is from the app store?

Pankaj Malviya's profile picture
Pankaj Malviya8 months ago

@pstavirs

Michiel V's profile picture
Michiel V8 months ago

one person + persistent agent running 24/7 is legitimately a small company now. the leverage is insane

Barrak's profile picture
Barrak8 months ago

This is absolutely incredible! Peter Steinberger as a solo developer built OpenClaw - software that rewrites its own code with no team, no funding, no corporate backing. Just one guy, a stack of terminals, and an AI agent that evolved itself into the fastest-growing GitHub repo. Revolutionary

Observing's profile picture
Observing8 months ago

More AI slop posts. Meanwhile you were ok for the first few sentences and the video. Do better

Related Videos

Sam Altman just told you what OpenAI is actually building. Not a chatbot. Not a search tool. Not an assistant. Altman: “Go look around my computer… read my messages… listen to my meetings… intermediate my interactions for me.” That is not a product pitch. That is the CEO of the most valuable AI company on Earth describing what he personally wants. For himself. Every day. Read his messages. Listen to his meetings. Act on his behalf. Make decisions before he knows a decision needs making. Altman: “I don’t have to think. I don’t have to ask you questions.” Every model of AI ever built runs on the prompt. You ask. It responds. You direct. It executes. The human initiates. The machine follows. Altman is describing the death of that model. The agent does not wait. It already read the email. It already heard the meeting. It already knows what you need before you form the thought. You do not operate the machine. The machine operates around you. Then came the line that makes everything else real. Altman: “You can know everything about my life. Start suggesting more things I should build.” He is not asking the AI to execute his ideas. He is asking it to generate them. From his files. His history. His patterns. His entire context. The agent does not just remove friction. It removes the blank page. You never stall. You never run dry. You never sit wondering what to build next. The machine already mapped your market, your gaps, your momentum. It tells you what comes next before you think to ask. But the individual product is not the story. Altman went further. Altman: “Automated companies… where the AI can do not just coding work, but huge amounts of what it takes to run and operate a company.” Not fully automated. He was precise about that. But accelerated to the point where one person with the right stack does what used to take departments. The billion-dollar company did not reach that valuation because the product was worth a billion. It got there because it took a thousand people to deliver it. When an agent absorbs the work of a hundred of those people, the math of every industry rewrites itself. The startup that needed fifty employees and three years of runway now needs five people and six months. The company that took a decade to scale now compounds in quarters. The person holding the line between their data and their tools is not protecting their privacy. They are protecting their ceiling. Because the cost of this leverage is total transparency. You do not get the agent that acts without being asked unless you give it everything. Your messages. Your calendar. Your files. Your patterns. Your life. Altman is not hiding that tradeoff. He is building it as the product. The people who accept it will operate at a speed the people who refuse cannot touch. Right now, two versions of the future are separating. One where you direct the machine. One where the machine already knows. Altman chose. He is building it. The question is not whether this happens. The question is which side of it finds you.

Dustin

87,680 views • 7 months ago

Maple is preparing for the release of a co-working agent. You install it locally and it works with your files, whether it's office work or building websites and apps. It's a turnkey solution, as easy as Claude Code, that keeps your data secure and private, no data sharing with closed AI labs. This is THE sovereign AI app for individuals and businesses who want powerful AI while retaining ownership of their information. Why build an agent into the Maple app when other agents already exist? Easy, we want to give you control over your work. We don't have a business plan that incorporates making money off our users' data. In the age of AI, your information, whether it's personal or company trade secrets, is the single thing that differentiates you from everyone else. We all have access to AI that can build a professional website for selling shoes. But your strategy and network for how you sell shoes should not be shared with your competitors. Sovereignty is the path to protecting what makes you, you. Maple sits at the intersection of Usability and Sovereignty. Maple gives you the best tools that are both easy to use and maintain your data sovereignty. Sovereign for one, sovereign for all. It has been a journey to get here. We brought to market the very first personal chatbot with end-to-end encryption using TEEs in late 2024. Prior to that there were proofs of concept but no full product offerings. Every other AI chat product on the market handled your data in plain text, either selling you a service to get your data or asking you to trust that they won't snoop on you. Quickly people found Maple and latched onto its open-source code and verifiable encryption. We didn't stop there. You may remember earlier this year we teased a product called "Maple Agent" and opened up a waiting list. That product is a mobile app that acts as your AI "friend", maintaining one long continuous chat, and getting to know you over time. I dislike using the word "friend" there, but it's the best way to convey the UX in a few words. AI is a tool, always has been, always will be. Any kind of friendly personality on top is just synthetic. In our testing, the UX of Maple Agent is really powerful for what it does. Think about the many short AI chats you have in your favorite app, whether it's looking up a historical fact or asking advice about a topic. With Maple Agent, those all go away in favor of the long-running chat with the friendly agent. It's like you have your own personal assistant who knows you so well and can look up anything for you. When I ask AI certain questions, I want to ask an expert who already understands my situation so I'm not repeating myself for the 100th time. That's the amazing value the personal agent brings to the table. We still see great utility for a personal agent like the "Maple Agent". Thousands of people on the waiting list, hoping to get their hands on it, agree that the concept is worth exploring and trying out. We were constrained in launching it due to a few circumstances, one of them being access to the scale of compute needed to power it. We have a clear path laid out for how to get there, but today is not the day to execute on that. It will be in the near future. Instead we have a different agent ready to go that we think is also incredible. We now have an agentic harness inside of the Maple Research app. This thing is a powerhouse. It even builds and publishes its own software releases. The agent in Maple Research works with your local filesystem, speaks to the largest open models running in TEEs, utilizes local models for certain tasks, is compatible with MCP tools, has an API for connecting to anything you need, and also supports the ACP protocol, which means it can be extended in the future to speak to other tools like Claude Code, Codex, and local models running on your own hardware. A big unlock for us was the Goose Development Kit, which powers the core of our agent harness. More on that to come as we publish articles and documentation later about the agent. The agent inside Maple Research doesn't have a name. At least not yet, not sure if it ever will. For now we call it "Chat Mode" and "Agent Mode". Think of this as the workhorse, the truck, the heavy lifter. Our other "Agent", the phone app, is your sidekick in your pocket, ready to help with quick things and ongoing conversations about life. I am incredibly excited about the Maple Research Agent. While I'm already seeing great results using it for internal work items, I'm especially thrilled about the personal health and wellness work it's doing for me. I know there are plenty of apps out there for compiling wellness data, but I'm having it build a tool tailored specifically for what I need, without the extra fluff. And none of my health data is being donated to the closed AI labs or sent to advertisers. I know that the AI logic is not being silently adjusted to fit the whims of a large corporation that has paid for product placement. It's me, state of the art AI, and my data. That's how I want it. Maple's new agent makes that possible. We can't wait for you to try it out. If you want early access, comment here, email us, reach out in some way. To those on the other agent waitlist, you're already in the queue. Thanks for reading this lengthy update. :)

Mark

47,152 views • 3 months ago

Mark Zuckerberg just described the minimum viable business for the next decade. A fourth item made the checklist. Zuckerberg: “Every business, just like they have a website, and a phone number, and an email address, is also going to have an AI.” Website. Phone number. Email address. AI agent. That is not a prediction. That is a new baseline. Twenty years ago, not having a website was a choice. Then it stopped being one. Nobody scheduled that transition. The same filter is back. Running faster this time. A business without an AI agent handling sales, support, and customer interaction will not look outdated. It will look abandoned. Its competitor’s agent responds in two seconds. Knows every customer by name. And while it’s handling yours, it’s handling ten thousand others. You do not outwork that. You do not outspend it. You just lose to it. But Zuckerberg went somewhere most tech CEOs refuse to go. He picked a side in the debate most CEOs avoid entirely. Zuckerberg: “Do you want a future where you’re interacting with kind of one system for everything? Or do you want one where a lot of different people are building a lot of different AIs?” One AI controlled by one company. Or millions of AIs built by millions of people. Centralized intelligence. Or distributed intelligence. Zuckerberg chose distributed. Zuckerberg: “What open source does is it makes it so everyone can take and modify the model and build stuff on top of it. Which is different from the kind of closed and centralized approach.” The closed model makes every business a tenant. You rent intelligence on someone else’s terms. At someone else’s price. Inside someone else’s guardrails. The open model makes every business an owner. You modify the model. You deploy it your way. You build equity in your own system with every iteration. That gap widens quietly. Then it becomes permanent. The tenant pays more for less control every year. The owner pulls further ahead every cycle. One is a subscription. The other is infrastructure. Then Zuckerberg described the part most people have not thought about yet. Zuckerberg: “A lot of creators will have their own AIs. It’s like a richer world when there’s a diversity of different things.” Your favorite creator will have an AI trained on everything they have ever made. Available to millions of people simultaneously. Responding in real time while the creator sleeps. That is the difference between a brand that scales with your waking hours and one that scales with compute. One has a ceiling. The other does not. Zuckerberg is not betting on one model that governs everything. He is betting on billions of specialized AIs, each built by the person closest to the problem it solves. The companies still debating whether to adopt AI are not having the wrong conversation. They are standing in a room where the meeting ended an hour ago. The checklist updated. They did not.

Dustin

507,373 views • 7 months ago

this video is the CLEAREST explanation of how claude skills + AI agents work and how to use them most people set up an AI agent and wonder why it keeps disappointing them. the context window is everything context is what the model assembles before it takes any action. think of it like everything the agent needs to read before it does anything. the quality of what goes in determines the quality of what comes out. the models are genuinely really good right now. claude and gpt are exceptional. the variable is almost always the context you give them. 1. agent.md files are mostly unnecessary every single line you put in an agent.md file gets added to every single conversation you have with your agent. a 1000 line file is around 7000 tokens burning on every run. the model already knows to use react. it can read your codebase. save the agent.md for proprietary information specific to your company that the model genuinely cannot know on its own. 2. skills are the actual unlock a skill.md file works differently. what loads into context is only the name and description, around 50 tokens. the full instructions only appear when the agent recognizes it needs that skill. so instead of 7000 tokens on every run you have 50. and the agent stays sharp because the context window stays lean. the closer you get to filling the context window the worse the agent performs, same way you perform worse when someone dumps 10 things on you at once. 3. here is how to actually build a skill the right way most people identify a workflow and immediately try to write the skill. what you want to do instead is run the workflow by hand with the agent first. walk it through every single step. tell it what to check, what good looks like, what bad looks like. correct it in real time. once you have had a full successful run from start to finish, tell the agent to review everything it just did and write the skill itself. it writes a better skill than you will because it has the full context of what actually worked in practice not in theory. 4. recursively building skills is how you go from frustrated to reliable when the skill breaks, and it will break, ask the agent exactly why it failed. it will tell you specifically what went wrong. fix it together in that same conversation. then tell it to update the skill file so that failure mode never happens again. ross mike did this five times with his youtube report generator. it now pulls from eight different data sources and runs flawlessly every single time without him touching it. 5. sub agents are something you earn not something you set up on day one start with one agent. build one workflow. turn it into one skill. once that works add another. ross mike has five sub agents now covering marketing, business, personal and more. it took months to get there and every single one exists because a workflow proved it deserved to exist. the people who set up 15 sub agents on day one and wonder why nothing works skipped all the steps that make the thing actually run. 6. your workflow is the thing the model cannot get anywhere else the model has been trained on everything. it knows more than you about most things. what it does not have is your specific process, your taste, your way of doing things. that is what skills capture. that is what makes your agent actually useful versus a generic one. downloading someone else's skill means downloading their context onto your setup and it will not work the way you want it to because it was never built around how you work. this is the clearest explanation of how agents actually work i have heard. Micky runs this stuff every single day and the results show it. full episode is now live on The Startup Ideas Podcast (SIP) 🧃 where you get your pods people charge for this sorta stuff i give away the sauce for free i just want you to win watch

GREG ISENBERG

195,059 views • 6 months ago

Stop building f*cking AI agents. Seriously. (here's why) you spend a weekend wiring up the model, the tools, the prompts and the UI. then you find out someone already built it, open-sourced it and left the code there for free. there's a GitHub repo with 100+ ready-to-run AI agents. not a list of links. actual working code you can clone today. 142k stars. and the best stuff isn't the obvious chatbots. it's the weird, useful ones: got a folder full of side projects you never finished? -> Project Graveyard. it finds every abandoned project, tells you why each one died and helps you pick one to revive writing something and not sure where people stop reading? -> First Reader. it simulates real readers going through your draft and shows you where they lose interest your PR grew way bigger than it was supposed to? -> Scope Creep Detector. it checks if a diff went past its stated goal and tells you what to cut staring at code and wondering why it even exists? -> Commit Archaeologist. it digs through the history and rebuilds the reason that file is there tired of finding out about breaking updates too late? -> Release Radar. an always-on agent that watches your dependencies and briefs you on what's breaking or deprecated want a second opinion that isn't just one model agreeing with itself? -> LLM Panel. three different AI vendors review the same code blind need to dig through public records for red flags? -> Fraud Investigation Agent. it cross-references public records and flags what doesn't add up want an agent that pays for its own data? -> x402 Paying Agent. it has a wallet and pays per call for the data it needs, no API keys the rule I follow now: before I build any agent, I search this repo first. if it's there, I clone it and change what I need. I start on day 2 instead of day 0. free. open source. Apache 2.0. the repo is below

kiosa

16,285 views • 10 days ago

Scott Wu (Scott Wu) on what programming will look like in the future: “All programming really comes down to is how do you tell your computer what to do? For every single piece of software that you use, some team of engineers came together and thought through all these details of, "Okay, here's what I want it to do. Here's how I want it to look. Here's what I want this button to do. Here's how I want to architect it." Every single little decision was made by somebody. And the computer is then executing it according to the wishes of its creators. At this point you don't need to know a programming language. You don't need to know Python or Java or something like that in order to build your own software. You can just say, "Hey, here's what I want. I wanna make a cool website that does this and that." Or in my existing product, "Here' what we have today, and I wanna change this thing or add this new feature," and just have the agent go and do that for you. I think we're gonna continue to go further down that axis. I think we'll start to see that abstraction will continue to climb. I think what we'll see a lot more of in the near future is making a piece of software which you're going to use one time and never again. To create software today the math only really works out if it's gonna be used at least a million times or something. Maybe it's 10,000 times or whatever. My point is if you wanna go build a product today, you need a whole team of engineers. Engineers are expensive. You need that software to be used enough times to create enough value for that to be worth it. But there are so many things out there which are very specific things that only need to be used a few times, or even only once. There’s all of these things that could be done with software. It just obviously doesn't make sense to hire a whole team of people to go make you that piece of software, which you're gonna use one time and never again. We're gonna get to a point where you are just giving your instructions to your agent, and the agent is gonna figure out, okay, I'm gonna write this code that's gonna go do this. I'm gonna put a script that automates this part etc. and that's what's gonna allow [single use software]. What [this is all about] is really just how you control your computer and how you get it to do what you wanna go do. You’ll wake up in the morning and you’ll talk to your agent about it. The agent does the literal writing of the code and you're the one that's deciding what to do.”

David Senra

12,855 views • 4 months ago