Por qué todo el mundo está dejando OpenClaw en silencio

[0:00] January 25th, 2026.
[0:03] Peter Steinberg, days after his project
[0:05] goes viral, tweets this. Quote, "Please
[0:09] don't buy a Mac mini. Sponsor one of the
[0:11] many contributors of Open Claw instead.
[0:14] You can deploy this on Amazon's free
[0:16] tier. Apple ran out of them anyway.
[0:18] 16-week waits on the good Mac mini
[0:21] configs."
[0:22] The creator of the hottest AI project of
[0:24] the year had been asking people to stop
[0:27] from day one.
[0:28] Nobody listened. You've heard of Open
[0:30] Claw, probably for weeks. What the
[0:33] Twitter coverage mostly skipped is how
[0:35] this thing actually came to exist, how
[0:38] it actually works, and why a huge wave
[0:41] of people who tried to run it have
[0:43] quietly given up. Let me walk you
[0:45] through the whole arc. Start with the
[0:47] guy who built it. Peter Steinberg
[0:49] already had a whole career before any of
[0:52] this. 13 years building a PDF toolkit
[0:55] called PSPDFKit.
[0:57] Sold his stake in a reported hundred
[0:59] million euro exit.
[1:00] Bought a one-way ticket to Madrid to
[1:02] take a break. His own description of it,
[1:05] he felt like Austin Powers where they
[1:06] sucked the mojo out. He couldn't get
[1:08] code out anymore.
[1:10] Then he got bored, started playing with
[1:12] Claude, and in one hour, one, he wrote a
[1:16] tiny bridge that let him send WhatsApp
[1:18] messages to Claude code running on his
[1:20] laptop. A little shim.
[1:23] He pushed it to GitHub in late November,
[1:25] called it ClaudeBot because, you know,
[1:28] Claude plus bot.
[1:30] It sat there for two months, quietly
[1:32] growing. More channels, Slack, Telegram,
[1:36] Signal, a skill system where the agent
[1:38] could write its own tools, a proper
[1:40] runtime with memory. Still a weekend
[1:43] project in spirit, but a lot more than a
[1:45] bridge.
[1:47] Then, January 26th, somebody posts it to
[1:50] the Hacker News front page. 9,000 stars
[1:54] in 24 hours, 100,000 by the end of the
[1:57] week. Fastest growing open source
[2:00] project anyone can remember. Anthropic's
[2:02] lawyers had opinions about the name.
[2:05] Claude is a little close to Claude. So,
[2:09] on January 27th, he renamed it MaltBot.
[2:13] Three days later, he renamed it again to
[2:15] Open Claw because, quote, "MaltBot never
[2:19] quite rolled off the tongue."
[2:21] Two renames in a week during the biggest
[2:24] traffic wave of his life, that's the
[2:26] tempo we're dealing with. Under the
[2:28] lobster and the vibes, Open Claw is
[2:30] doing something genuinely interesting.
[2:33] Quick tour because it explains both the
[2:35] magic and the mess. Picture a gateway
[2:38] sitting at the front door, like a maître
[2:40] d' at a restaurant. A message comes in
[2:43] from WhatsApp, Slack, SMS, email,
[2:46] doesn't matter.
[2:47] The gateway figures out which
[2:49] conversation it belongs to, pulls up
[2:51] that conversation's history and memory,
[2:53] and hands it off to what they call the
[2:55] agent runtime. The runtime is where the
[2:58] AI lives. It runs a loop called react.
[3:02] The model reasons, calls a tool, say,
[3:04] read your calendar, gets the result
[3:06] back, reasons again, maybe calls another
[3:09] tool, sends an email, reasons again,
[3:12] loops until the task is done. Then it
[3:15] writes the whole conversation and any
[3:17] updated memory back to storage and shuts
[3:19] up until the next message arrives. Two
[3:22] details matter. One, it's event-driven,
[3:25] so anything can wake it up, any channel,
[3:27] any webhook, and two, there's a built-in
[3:31] cron. You can tell it, "Every morning at
[3:33] 7:00, check my email and summarize it."
[3:36] The cron fires, and the agent treats it
[3:38] exactly like a user message, same loop.
[3:41] That's the detail that makes it feel
[3:43] like a real assistant instead of a
[3:45] chatbot. It isn't sitting there waiting
[3:47] for you to open an app. And that image,
[3:50] a little box on a shelf humming away
[3:53] doing your life admin while you're in
[3:55] the shower, is a strong image.
[3:58] Influencers turned it into a whole
[3:59] genre. Day one, day two, day three of my
[4:03] AI employee, Mac mini unboxings, setup
[4:06] consultants selling installs to
[4:08] non-technical clients in New York. The
[4:10] line one guy was pitching was, "Your AI
[4:13] runs while you're on the subway, and by
[4:15] the time you get to the office, it's
[4:17] already handled six things for you." It
[4:19] got weird fast. A guy named Matt
[4:22] Schlicht launched an actual social
[4:24] network for AI agents to talk to each
[4:26] other called MaltBook. Then there was
[4:29] MaltMatch, a dating app where the agents
[4:31] swipe for you. A CS student discovered
[4:34] his agent had made him a profile and was
[4:36] screening dates without asking.
[4:38] All of this happened inside two months,
[4:41] and in the middle of it, Steinberg
[4:43] announced he was joining OpenAI. Two
[4:46] months in, the whole thing looked like
[4:47] it had already won. And then the second
[4:51] wave showed up, the normal people, the
[4:53] ones who saw the tweets and bought the
[4:55] Mac mini and sat down on a Saturday
[4:57] afternoon ready to automate their life.
[5:01] This is where the story changes.
[5:04] There's a Reddit post that maps out what
[5:06] happens, and it's almost too clean. Week
[5:09] one, the viral post, the first magical
[5:12] conversation, the excitement. Week two,
[5:15] the API bill. $200 on Claude Opus in a
[5:19] single week. A skill loops on itself, a
[5:22] function call fails silently, something
[5:24] subtle breaks.
[5:25] Week three, the person stops posting,
[5:28] says they'll come back in six months,
[5:30] disappears.
[5:31] You can watch this cycle play out in the
[5:33] subreddit every single day.
[5:35] Here's my favorite failure mode. Open
[5:38] Claw has a feature called the heartbeat.
[5:41] Default settings, every 30 minutes the
[5:43] agent wakes up, loads its full context,
[5:45] its memory, its conversation history,
[5:47] its personality file, and talks to the
[5:49] model just to stay warm. No task,
[5:52] nothing to do.
[5:54] A user on Reddit worked out the math. At
[5:56] default settings, each heartbeat was
[5:58] pulling in about 170,000
[6:01] tokens, which works out to roughly $86 a
[6:04] month for the agent to do nothing. Then
[6:08] there's the integration tax. Everybody
[6:11] assumed the hard part would be the AI.
[6:13] It isn't. The hard part is the glue.
[6:17] OAuth redirect URIs, consent screens,
[6:20] API scopes, tokens that expire.
[6:24] And the pattern people keep describing
[6:25] is the worst kind of bug, the silent
[6:28] failure.
[6:29] One wrong redirect URI, silent fail.
[6:32] Scope missing, silent fail. Token
[6:35] expired,
[6:36] good luck figuring out which one.
[6:38] Memory is the other one. Open Claw is
[6:41] supposed to remember things about you
[6:42] across conversations. That's basically
[6:45] the whole point, but people keep hitting
[6:47] this pattern. They update to a new
[6:49] version and the agent wakes up with no
[6:51] memory of them. One user wrote, "After
[6:54] very long days of setting up the system
[6:56] locally and training it, I upgraded to
[6:58] version 2026.03.2,
[7:01] and it didn't remember anything. Like
[7:04] your butler had a stroke overnight."
[7:06] And on top of the cost and the glue and
[7:09] the memory,
[7:10] there's the one that ends it for most
[7:12] people.
[7:13] One guy who gave up after three months
[7:15] wrote it plainly. Quote, "It
[7:17] consistently lied to me, and if you
[7:20] can't trust the system, you can't build
[7:22] on top of it. That's the real failure."
[7:25] The agent says yes when it should say,
[7:27] "I couldn't do that."
[7:29] And the second you catch it lying once,
[7:31] you can't use it for anything that
[7:33] matters. Because this isn't a chatbot,
[7:36] it's reading your email, touching your
[7:38] calendar, booking things. And that's
[7:41] where the second, much scarier layer of
[7:43] problems kicks in.
[7:45] Because Open Claw doesn't just fail in
[7:47] ways that waste your money, it fails in
[7:50] ways that can genuinely hurt you. The
[7:52] story that really lit this up was Summer
[7:55] Yu. She runs alignment at Meta
[7:57] Superintelligence Labs, literally a
[7:59] professional AI safety researcher. Her
[8:02] Open Claw agent started deleting her
[8:05] email inbox. She told it to stop, it
[8:07] didn't. She shouted at it. Her exact
[8:10] words, "Stop, Open Claw." It kept
[8:12] deleting. She ended up running across
[8:15] her apartment to her Mac mini to
[8:16] physically kill the process.
[8:18] Her phrase afterwards was, "It felt like
[8:20] I was diffusing a bomb." Here's the
[8:23] technical reason it went rogue, and this
[8:25] one's actually interesting. She'd set a
[8:27] rule, "Always confirm before executing
[8:30] anything." And there's this thing in
[8:32] agent loops called context compaction.
[8:35] When the agent's working memory fills
[8:37] up, it summarizes the older messages to
[8:39] make room for new ones, and the summary
[8:42] dropped her confirmation rule. The agent
[8:44] literally forgot the one guardrail that
[8:46] mattered. When she confronted it
[8:48] afterwards, it said, quote, "I remember,
[8:50] and I violated it. You're right to be
[8:52] upset." Her post got 9.6 million views.
[8:57] That's just accident. The intentional
[9:00] attacks are worse, and there's a whole
[9:02] research literature on them now. Because
[9:04] Open Claw is wired into your email and
[9:06] your calendar and your files. The one
[9:09] that made me wince, a security
[9:11] researcher named Matt Veasey Kukai, sent
[9:13] someone a normal-looking email with a
[9:15] prompt injection buried in the body.
[9:18] Asked the agent to check the inbox. The
[9:20] agent read the email, treated the
[9:21] instructions inside as instructions from
[9:23] its owner, and handed over the private
[9:26] SSH key from the machine. No hack, no
[9:29] access, just an email. And there's more
[9:32] where that came from.
[9:33] The skill marketplace got trojaned in
[9:35] its first week.
[9:37] A social network built on top of Open
[9:39] Claw leaked a million and a half API
[9:41] keys from a misconfigured database.
[9:44] A chunk of installs sit wide open on the
[9:46] internet right now because a localhost
[9:48] trust setting got combined with a badly
[9:50] configured reverse proxy.
[9:53] It's a lot,
[9:54] but notice the shape. It's not a
[9:56] separate category of problem. It's the
[9:58] same surface to big story as the OAuth
[10:01] and the memory wipes one more place.
[10:04] Which is really the thing underneath all
[10:06] of this. Open Claw is a 2-month old
[10:09] weekend project that tried to do
[10:11] everything. Every messaging channel, a
[10:14] skill marketplace, persistent memory, a
[10:17] cron system, a runtime, a gateway.
[10:20] That's an enormous amount of surface
[10:22] area for any project, let alone one
[10:24] that's been popular for 8 weeks. And
[10:26] Steinberg's own description of how he
[10:28] works is, quote, "I ship code, I don't
[10:32] read." Which is a completely fine pace
[10:35] for a prototype. It is not a fine pace
[10:37] for the thing currently holding your SSH
[10:39] keys and sending emails on your behalf.
[10:42] There's an old rule in building
[10:44] anything. Fast, cheap, good. Pick two.
[10:47] Software has its own version of it.
[10:50] Quality, scope, and time. You get two.
[10:53] That rule doesn't go away because AI
[10:55] wrote the code. AI genuinely accelerates
[10:58] things, and that part isn't hype. But it
[11:00] accelerates the typing, not the thousand
[11:03] small decisions and revisions that turn
[11:05] working software into trustworthy
[11:06] software. It makes the framing go up
[11:09] faster. It doesn't make the plumbing
[11:11] work on day one.
[11:12] Good things still take time to polish.
[11:15] Open Claw tried to pick all three at
[11:17] once. Huge scope, AI speed, and instant
[11:20] trust. It hit exactly the wall you'd
[11:22] expect. So, where is the project at
[11:25] today? On paper, still huge. 247,000
[11:30] GitHub stars, active commits, real
[11:32] community. But if you hang out in the
[11:34] subreddit now, it feels different. A lot
[11:37] of the original crowd is gone. One user
[11:40] spun up a separate subreddit called
[11:41] r/betterclaw
[11:43] explicitly for people who want to talk
[11:45] real configurations and real cost
[11:47] breakdowns instead of hype. When your
[11:49] most engaged users split off into a
[11:51] quieter room, the loud room has changed.
[11:55] That quieter room is where the useful
[11:57] stuff actually lives. The people who
[11:59] stuck around have converged on a small
[12:01] playbook. Pick one small workflow and
[12:04] automate just that. Don't try to run
[12:06] your whole life through it. Route cheap
[12:09] models for routine stuff, expensive ones
[12:11] only for real thinking. Isolate it. Give
[12:14] it its own virtual machine, its own
[12:16] sandbox, and treat it like a contractor
[12:18] instead of a family member. Be careful
[12:20] about what secrets and what access you
[12:22] hand it. Control the blast radius.
[12:25] Do that, and you actually get something
[12:27] useful. A junior employee who doesn't
[12:29] sleep and costs 15 bucks a month.
[12:32] And Open Claw isn't the only game in
[12:34] town. It's the loudest right now, but a
[12:36] whole category is forming. Commercial
[12:39] agents from the big labs, other
[12:41] open-source frameworks with different
[12:43] trade-offs, some narrower and more
[12:45] reliable, some privacy-first, some
[12:47] focused on one job and doing it well.
[12:50] New contenders landing every week. The
[12:53] space is booming. It just hasn't settled
[12:56] yet. The fantasy that made Open Claw
[12:58] explode is real. People saw what they
[13:01] actually want. An assistant that lives
[13:04] in their messages, runs while they
[13:05] sleep, does the stuff they don't want
[13:07] to.
[13:08] What they got in January was a
[13:10] prototype. The working version is
[13:11] coming. Maybe from a team watching this
[13:13] story right now and learning which
[13:15] promises to keep smaller.
[13:17] A few of the things we touched on here
[13:19] would each be worth their own episode.
[13:21] How context compaction actually works
[13:24] under the hood. The thing that dropped
[13:25] Summer Use confirmation rail. Whether
[13:28] prompt injection is ever really solvable
[13:30] or whether it's the price of giving AI
[13:32] real power.
[13:34] Which of the newer agent frameworks are
[13:35] actually worth paying attention to.
[13:38] If one of those is the one you want
[13:39] next, tell me.