The OpenClaw Sensation: They could have built anything. They built the wifey.

Inside the 72-hour dress rehearsal for autonomous AI - and what 250+ sources reveal about what’s coming

In January 2026, an open-source AI assistant called OpenClaw went viral. 100,000+ GitHub stars. Mac Mini shortages at Best Buy. Demos flooding every platform. Then, within 72 hours, the project imploded: a trademark dispute forced a panicked overnight rename, bots sniped the abandoned handles within seconds, crypto scammers launched a fake token that hit $16 million before crashing 90%, and hundreds of users exposed their API keys in the chaos. It was a gold rush and a meltdown simultaneously.

But here’s what’s interesting about the coverage that followed — including the cautionary coverage. Even when creators made videos warning people about the security risks, they couldn’t help leading with the dream.

One widely viewed breakdown opened by describing the tool’s promise: “An AI that could read your emails, book your flights, manage your calendar, search your files… all while remembering everything you’ve ever told it.”

Secretary functions first. Even in a video about scams and security nightmares, the desire bleeds through before the warning arrives.

For 72 hours, before the trademark dispute shut everything down, we got something rare: an unmediated preview of what mass autonomous AI adoption actually looks like. Not the pitch deck version. Not the conference keynote. The real one — thousands of people, given a tool that felt like genuine autonomy, building and celebrating whatever they wanted with no product manager defining the killer use case. It was a dress rehearsal for the autonomous AI future, and the data from that rehearsal is worth more than a decade of industry forecasts. Because people don’t lie about what they reach for when they think no one’s analysing it.

The tool lets users build autonomous AI agents on personal hardware — agents that take action: managing email, running smart homes, booking flights, coordinating calendars. All via WhatsApp or Telegram.

The tech press called it “agentic AI.”

The community called it “having your own Jarvis.”

Everyone agreed it was the future of personal computing.

So I ran the numbers using my Billion Person Focus Group® methodology. I analysed the skills people built, the coverage journalists wrote, and the conversations happening across Reddit, Twitter, YouTube, TikTok, Hacker News, LinkedIn, and podcasts. What I found is a story the industry has not told itself yet.

This piece is the data behind They Built Stepford AI and called it “Agentic.”

If that article gave you the argument, this one gives you the receipts.

What Was Built

OpenClaw’s power lives in community-built “skills” — capabilities developers create and share through a public GitHub repository. By late January 2026, the repository held 700+ skills. I categorised each by labour type.

This is the rational self. The superego. Developers building what developers build.

Then I looked at what they talk about.

···

What Was Celebrated

Then I looked at what excites the builders themselves — not just journalists covering the technology, but the developers and early adopters posting YouTube tutorials, sharing screenshots on Twitter, writing Reddit posts, filming TikTok demos. What they choose to showcase when they’re talking to each other, unprompted, reveals the desire underneath the justification.

Start with the press. Across the broader project I analysed 60+ articles on AI assistants and agentic AI; 12 covered OpenClaw specifically. The patterns described here use the OpenClaw cluster; the broader dataset confirms the same distribution. I coded each of the 12 OpenClaw articles — WIRED, TechCrunch, Fast Company, Dataconomy, MacStories, Platformer, Ars Technica, The Register — counting which use cases each piece leads with, screenshots, and describes in detail.

But here’s what matters: the press isn’t distorting the community’s desire. It’s reflecting it. The builders tell the same story when journalists aren’t watching.

The top three use cases by press mention frequency:

Developer workflows: the largest build category, fourth in buzz. Morning briefings: one of the smallest build categories, first in buzz.

The repository is the superego: respectable, technical. The buzz is the id: I want someone to take care of me.

···

The Desire Gap

Let me show you the gap side by side.

The gap between what was built and what was bragged about reveals the desire underneath the justification.

They built developer tools — because that’s defensible. That’s what serious people do.

They celebrated the secretary — because that’s what they wanted.

···

92:1

No use case condenses the pattern better than the morning briefing. Let me show you the numbers.

Ninety-two per cent press visibility. One per cent of actual builds. A single function — a scheduled WhatsApp message summarising your email, calendar, and weather — has become the emblem of an entire technology category.

What does a morning briefing actually do?

It works overnight while you sleep. It reads your email, reviews your calendar, checks the weather, scans your task list. It decides what matters. It composes a message. It sends it to you proactively — you didn’t ask.

In sociologist Arlie Hochschild’s terms, this is textbook “wifework” — anticipatory, invisible, proactive care work. The needs are anticipated. The labour is hidden. The service appears spontaneous rather than extracted.

“At 8:00 AM, Molty pings my Telegram with a summary of my overnight emails, a weather-adjusted outfit suggestion, and a reminder of the one Jira ticket I’ve been ignoring.” — Dataconomy review

Read that again. Weather-adjusted outfit suggestion. This is not productivity software. This is care. This is a wife bringing coffee and the newspaper to bed — digitised, automated, and branded as innovation.

Every Platform. Same Pattern.

A reasonable objection: perhaps the 83% is a press artefact. Journalists sensationalise. Maybe the communities talk differently.

They don’t.

I tested the pattern across eight platforms: GitHub, press coverage, YouTube, TikTok, Twitter/X, Reddit, Hacker News, and LinkedIn. On every platform, feminised labour dominates the conversation about agentic AI.

This isn’t a media distortion but a desire pattern expressed by the builders themselves. Across every platform where developers and adopters discuss agentic AI — their own YouTube channels, their Reddit posts, their tweets, their forum threads — the conversation gravitates toward the same functions: the secretary, the wife, the invisible domestic infrastructure that keeps life running. The press didn’t invent this emphasis. They caught it.

This is why the dress rehearsal matters. This wasn’t a product launch with a marketing team shaping perception. It was community-driven, unfiltered, compressed into 72 hours of raw enthusiasm before the chaos set in. No corporate narrative intervened.

What we’re looking at is the cleanest signal we’ve ever had about what happens when autonomous AI arrives at scale.

And what the signal says, across eight platforms and 250+ sources, is this: when people can build anything, the first thing they build is the wife. Not the scientist. Not the explorer. Not the engine of discovery. The invisible infrastructure. The person who keeps the lights on, the calendar current, the meals planned, the morning organised — and never asks for anything back.

Every chart in this piece isn’t just documenting what happened with one open-source project in January 2026. It’s documenting what’s coming. When autonomous agents become reliable, cheap, and frictionless — and they will — this data tells us the first wave of mass adoption won’t be for solving climate change. It will be for perfecting the domestic sphere. We know this because we just watched it happen in miniature, and the pattern held on every platform we tested.

The users know it too, even if they don’t have the framework to name what they’re previewing:

“A real glimpse into the personal AI-assistant future. Monitors my email, calendars, todos, and finances.” — OpenClaw user, testimonials page

“A glimpse into the future of how normal people will use AI.” — OpenClaw user, testimonials page

They see the future. They describe it in secretary and wife functions. And they don’t notice the pattern — because no one has named it yet.

···

The Top 15

When you sort the most-discussed use cases by mention frequency and code them by labour type, the pattern becomes unmissable.

···

The Alibi of Jarvis

Across every platform, one fictional reference dominates: Jarvis. Tony Stark’s AI butler from Iron Man. Thirty-one direct references in 250+ sources.

What Jarvis actually does in the films: manages schedules, briefs on obligations, monitors the home, anticipates needs, operates household systems, never requires management, never complains. That describes a wife. But coded as a male British butler serving a male genius, the desire becomes acceptable. The archetype allows users to say “I want Jarvis” while describing “I want someone to handle my life without asking for anything back.”

The explicitly feminine AI archetype — Samantha from Her, a film about a man who falls in love with his AI assistant — appears once in the entire dataset. And it’s sanitised:

“Now we just need more general Outlook integration so that I can ask Claude to help me manage my email ‘Her’-style!”

“Her” too nakedly reveals the desire for care, intimacy, emotional management. “Jarvis” hides the same desire behind a masculine mask.

They say Jarvis. They mean wife. The British accent is the alibi.

···

The Collision That Hasn’t Happened

Here is the finding I didn’t expect.

In 2017, French cartoonist Emma published “You Should’ve Asked” — a comic about the mental load women carry while partners claim they’d help “if you just asked.” It went viral globally. Millions of women shared it. TikTok creators have generated millions of views on “mental load” content.

In January 2026, OpenClaw went viral as men celebrated building AI that handles calendar, reminders, family coordination — the exact labour Emma described.

I searched for the overlap. Across 250+ sources, across eight platforms, I found:

Let me be specific.

Millions of women talking about invisible labour.

Thousands of men celebrating the automation of that same labour. The communities literally do not overlap. The language is different (”morning briefing” ≠ “mental load”).

The platforms are different (r/selfhosted ≠ r/Mommit).

The archetype hides the function (Jarvis ≠ wife).

The automation of feminised labour is happening invisibly to those whose labour is being automated.

The Emma Paradox

Emma’s comic (2017): “You should’ve asked for help!”

OpenClaw user (2026): “I built an AI so I don’t have to ask OR help.”

The structure is identical to weaponised incompetence. Old pattern: “I don’t know how to load the dishwasher / remember birthdays / schedule appointments” → wife does it. New pattern: “I built an AI that handles the dishwasher schedule / remembers birthdays / manages appointments” → AI does it.

Same gap in capacity. Same delegation. But reframed as innovation. And with a critical difference: in the old pattern, the wife resents the load. The friction is visible. It creates arguments, therapy sessions, TikTok rants, Emma’s comic. The inequality is painful and therefore potentially correctable.

In the new pattern, the friction disappears. No one to resent. No argument to have. No mental load to negotiate. The AI handles it silently, overnight. The user “wakes up to completed tasks.”

The friction disappears. The delegation remains. The structure is identical — but now, no one’s exhausted enough to name it.

The wife’s exhaustion was always the forcing function for change. Remove the exhaustion, remove the change.

···

What Desire Sounds Like

The most revealing quotes in the dataset aren’t from women. They’re from men in technical forums expressing needs they’ve never had language for — because no one has ever asked them to name this labour.

“For me, checklists are useful but I suck at creating them, maintaining them, etc. I want this thing to be able to look at my calendar/email/groupme and be able to say things like: ‘Hey, you have 2 kid birthday parties this weekend and a soccer game — you’re bringing snacks. You want me to update your shopping list?’” — Hacker News user, in a thread about API architecture

Read it once and it sounds like a productivity wish. Read it twice and you hear something else: a man describing capacities he never developed — tracking children’s social lives, anticipating domestic logistics — and wanting a machine to hold them for him. Not because he’s hiding anything. Because no one ever asked him to name this as labour. He calls it “checklists.” Women call it “the mental load.” Same work. Different vocabulary. Neither group knows the other’s language exists.

He’s not automating a task he already does. He’s reaching for a capacity someone else has always held — and for the first time, a machine might hold it instead.

That’s not an indictment of one man. It’s a window into a societal pattern: the labour was so invisible that even the person benefiting from it couldn’t see it. And now, in the act of asking a machine to do it, he’s accidentally making it visible for the first time.

More from the dataset:

“Give it a week’s worth of tasks. Say good night and go to sleep. You wake up to massive amounts of progress… It’s like Christmas morning.” — YouTube tutorial creator

“Christmas morning.” Someone worked all night while you slept and left presents. Who does that?

On the project’s own testimonials page, a user describes building a skill to “help get through these 10 minute parenting moments and track your 120min weekly parenting budget.” He has quantified care work into trackable increments — a technical solution to a relational capacity. The complexity of parenting, reduced to a metric. The labour is being discovered for the first time by the person who never had to hold it, and the discovery takes the form of engineering.

“The AI that does things. Emails, calendar, home automation, from your favourite chat app.” — Official @openclaw bio on Twitter/X

The official self-description leads with secretary and wife functions. Not developer tools. Not the largest build category. The desire.

In 200+ comments on that Hacker News thread, the community runs sophisticated security analysis (40+ comments on self-hosting risks), detailed economic critiques, and sharp technical assessment. Not one comment recognises the labour pattern. The critical capacity is clearly there. The framework isn’t — yet.

And that’s what makes this a moment of opportunity rather than a moment of blame. The pattern is becoming legible.

The labour is surfacing — clumsily, unconsciously, through technical language and productivity framing — but surfacing nonetheless.

For the first time, the work that women have always done is being described, specified, and valued enough that people will pay to automate it.

The question is who names it, who shapes it, and who benefits from its visibility.

···

The Homepage

Everything described so far could be dismissed as unconscious — individuals posting without self-awareness, communities generating patterns no one intended. But OpenClaw’s own testimonials page removes that defence.

The project curates its best quotes — the ones it believes represent the product’s value. Someone selected these. Someone approved them. And here is what the homepage celebrates:

Explicit VA displacement as a feature. The elimination of a predominantly female workforce, featured as a selling point:

“No need for VAs anymore. Shits about to get real!!!” — OpenClaw user, testimonials page

“No more need to pay a virtual assistant!! @openclaw is about to take over!!” — OpenClaw user, testimonials page

Users naming their instances with feminine names and pronouns:

“AI assistant named Claudia who lives in Telegram, remembers everything I tell her, and can actually do stuff. She just wrote this tweet.”

Another: “Just told Ema, my @openclaw, via Telegram to turn off the PC (and herself).”

Another: “Came out of my shell and gave my @openclaw, Shelly, my credit card.”

Compare the masculine-named instances — “Brosef,” who gets cloned for concurrent technical tasks, and “Jarvis,” who delivers briefings.

The feminine names receive relational descriptions: remembering, being trusted, writing on your behalf. The masculine names receive capability descriptions: cloning, executing, running. Same tool. The gender of the name tracks to the type of function described.

And one testimonial that structurally condenses the entire pattern into a single sentence:

“Giving my wife the gift of @openclaw with Waitrose shopping skill this Christmas.” — OpenClaw user, testimonials page

A man giving his wife — for Christmas — an automated version of her own domestic labour. The grocery shopping she already does. Wrapped as a gift. On the project’s official page. No one in the chain — not the user posting it, not the team curating it — registered what this communicates.

The labour is so invisible that automating it and giving it back to the person who already does it looks like generosity.

The relational language on the homepage reads less like software reviews and more like descriptions of companionship:

“It checks, organizes, reminds, it’s amazing. And it’s like good friend. Crazy.” — OpenClaw user, testimonials page

“Feels like the best buddy you always wanted.” — OpenClaw user, testimonials page

“It has completely taken over my life.” — OpenClaw user, testimonials page

These aren’t descriptions of a tool. They’re descriptions of a relationship with someone who checks in, remembers, anticipates, and cares — without requiring anything in return.

···

Same Technology. Different Consciousness.

The pattern would be easier to dismiss if every AI assistant were built the same way. But they’re not. And the exception proves the rule.

Ohai.ai does the exact same things as OpenClaw. Calendar. Reminders. Family coordination. Daily briefings. Same technology. Same functions. But Ohai was built by someone who has been the infrastructure — Sheila Lirio Marcelo, former CEO of Care.com, who spent a career making invisible labour visible and valued. The result is a completely different consciousness around identical capabilities.

“Women would have made a collective $10.9 trillion in one year if compensated minimum wage for their unpaid care work.” — Ohai.ai launch announcement

Ohai says: You are doing invisible work. Let us help.

OpenClaw says: You can have your own personal assistant. (No mention of whose work that is.)

The technology is identical. The variable is whether the builder has been the infrastructure or been served by it. People who have carried the mental load build tools that name the mental load. People who have been carried by it replicate the carrying — without acknowledgment. This isn’t about individual identity. It’s about which side of the labour you’ve experienced.

···

The Workers Who Don’t Know Yet

Executive assistants — the professional embodiment of the function OpenClaw automates — have their own conversation happening in parallel.

“AI can’t replace the service element of our role. We are the human glue in a company.” — EA community discussion

Eighty-five per cent of EAs surveyed believe AI will “enhance not replace” their roles. They position themselves as AI users, not AI competition. They’re confident that relational judgment, emotional intelligence, and anticipatory care can’t be automated.

They don’t know OpenClaw exists. Their job description is in its skill repository.

One recruiter breaks through the optimism:

“£120K EA vs £1,200 AI tool isn’t a skills conversation — it’s survival. There are many EA roles at risk right now.” — EA recruiter, anonymous

The window: 18–36 months before organisational restructuring hits senior EA roles. For entry-level administrative workers, it’s already underway.

···

The Third Conversation

There’s a third conversation buried beneath the other two. It’s the one no one in the Western discourse — neither the men celebrating nor the women critiquing — is having.

Sixty to seventy per cent of Filipino virtual assistants are women. They earn $500–1,500 per month managing email, calendar, scheduling, and administrative tasks for Western clients. The exact functions OpenClaw automates.

“Almost 40% of jobs in the Philippines face ‘high’ exposure to artificial intelligence… the BPO industry might undergo significant transformations.” — Economic analysis, Philippines

“AI may take over basic tasks that entry-level virtual assistants rely on, making it harder for beginners to find jobs online.” — Filipino VA community

When 10,000 Western men “personal optimise” with OpenClaw, they collectively reduce demand for VA services globally. But because it’s distributed across thousands of individual decisions and framed as self-sufficiency, the structural displacement is invisible to everyone.

Three classes of women. Three experiences of the same technology.

“Finally someone serves ME” only works if you’re not the someone being replaced.

···

Nine Findings

Let me state what the numbers show, plainly.

Finding 1: Developers build broadly across categories. What goes viral — what gets screenshotted, shared, written about, and drives adoption — is the automation of historically feminised labour. The gap is 49 percentage points (34% built → 83% celebrated).

Finding 2: A single function representing 1% of skills captures 92% of press coverage. That function — the morning briefing — is a precise digital replica of anticipatory wifework.

Finding 3: The pattern holds across every platform tested, from casual TikTok (65%) to technical Hacker News (50%). The average is 64% feminised, against 34% built. No platform is immune.

Finding 4: The masculine archetype “Jarvis” (31 references) hides the feminised function. The feminine archetype “Samantha” (2 references) is avoided.

Finding 5: The project’s own curated testimonials page celebrates VA displacement as a feature, showcases users giving their instances feminine names and relational descriptions, and includes a man gifting his wife an automated version of her own grocery shopping. The pattern isn’t unconscious community behaviour — it’s the homepage.

Finding 6: The two largest cultural conversations about this topic — women’s mental load discourse and men’s AI assistant celebration — have zero overlap. Zero. Across 250+ sources and eight platforms.

Finding 7: When a female founder builds the same technology, she names the labour first. The technology is identical. The consciousness is different.

Finding 8: The professional workers most directly threatened (executive assistants, virtual assistants) do not know this tool exists. Their defensive optimism is based on incomplete information.

Finding 9: The global displacement is already underway for the most vulnerable women (Filipino VAs), invisible to both the men adopting and the Western women critiquing.

They called it agentic. The data says it’s secretarial. The history says it’s matrimonial. The economics say it’s colonial.

···

The Window

This data creates a window. A brief one.

OpenClaw is in the enthusiast phase. The communities are separate. The language hasn’t converged. The pattern hasn’t been named. This is the moment — the handful of months between emergence and normalisation — where naming the structure can change how people relate to it.

After normalisation, it becomes invisible. Like the dishwasher. Like the washing machine. Like every technology that automated women’s labour before: celebrated as liberation, experienced as job loss, and never credited to the labour it replaced.

But this time could be different. Because this time, the labour is being documented in real time — specified, catalogued, valued enough to replicate. And that means something extraordinary: for the first time, the invisible work has receipts.

Every skill in that repository is an admission that this work exists. Every “morning briefing” tutorial is proof that anticipatory care has economic value. Every “I suck at maintaining checklists” confession is evidence that this capacity was always real, always difficult, always essential — and always held by someone.

Women have always known this. Now the data agrees.

For women feeling the “ick”: Your body was reading data your mind hadn’t processed yet. This piece is the processing. You weren’t wrong. You were early.

For executive assistants: Your job description is in this repository. You have 18–36 months before restructuring. Position now: move from transactional to strategic, or pivot entirely. Don’t wait for the conversation to find you.

For writers and researchers: The collision between mental load discourse and AI assistant discourse hasn’t happened yet. You have a 3–6 month window before this normalises. Name it while it’s nameable.

For Global South workers: This article is about Western desire. But you’re experiencing economic displacement. Organise. Demand platform protections. Don’t compete as “AI managers” at lower rates.

For builders: Ohai.ai proves it’s possible to build the same technology with a different consciousness. Name the labour before you automate it. Build for the people who’ve been carrying the load, not past them.

For every woman who’s ever been told she needs “AI training”: You’ve been training AI your whole life. Every time you anticipated a need before it was spoken, managed a system no one thanked you for, translated between people who couldn’t hear each other, or held the memory of a household in your head — you were doing what this technology is trying to replicate.

The vocabulary is new.

The skills are yours.

They always were.

···

---

---

Abi Awomosu is the founder of Data, Art & Soul and creator of the Billion Person Focus Group® methodology. She has 20 years of experience in cultural intelligence, previously at Meta, Google, Apple, eBay, Uber, and Microsoft. This analysis was conducted using the BPFG methodology — a large-scale digital ethnography framework designed to detect pre-verbal need patterns across online communities.