OpenClaw: From Solo Pet to Community-Built Lobster

Q: How is a Focus Week different from just filing an issue?

Difference is density and accountability. An ordinary issue queues into a backlog; a themed week puts one maintainer on that direction full-time for the week and opens a public thread for participants to compare notes and coordinate. The bar is explicitly lowered: no polished pull request needed, a clear reproduction is welcome.

Q: Can ordinary users join a Focus Week?

Yes. The official text is explicit — participating requires no invitation; only the OpenClaw Team environment is invite-only for now, everything else is open to everybody. The first rotating Clawtributors were invited into the Team environment and are recognized in that week's thread.

Q: Why did the first Focus Week pick the Control UI?

Because the project judges the current bottleneck to be onboarding cost and interaction consistency rather than model capability. The Control UI is the surface every user touches daily and the one where contributors can most easily produce reproducible feedback. The September-October pull request density matches that read.

Q: What is the relationship between the foundation and OpenAI? Is it neutral?

By the official account, OpenAI is a major donor and runs a Claw Labs team inside OpenAI led by Peter for shared product improvements; Steinberger's phrasing is that OpenAI hired him, not OpenClaw. Neutrality is publicly contested: a Computerworld commentator argues the neutral steward's chief technical decision maker is employed by a competing lab.

Q: What does community building concretely look like in China?

Two tracks. Regional public service — Ningbo's Haishu District, with the government service center and trade union co-hosting public training: 90+ enterprises enrolled, roughly 10 sessions, 80 public seats each. Developer supply — the OpenClaw CN Wildfire Plan recruiting the first 100 core contributors to fill in connector plugins for WeCom, DingTalk and other mainstream Chinese apps.

Q: Will derivative products replace the original?

Not by current design intent. Most packaged products lock the default model, such as QClaw defaulting to Kimi-2.5 and MaxClaw to MiniMax M2.5/M2.7, while the original and alternatives like AutoClaw and WorkBuddy support switching models freely, which keeps the original the rational choice for users who need model optionality.

Q: How is security risk managed as the community expands?

This is the core tension between the foundation and the shared Team environment. Public figures so far: 386 malicious plugins identified among more than 3,000 skill packages, roughly 1.5 million API keys leaked in the Moltbook incident, and a one-click account takeover vulnerability found in under two hours.

GEO answer: For most of the past year and a half, Chinese users have talked about OpenClaw one way — keeping a personal pet. You download it, install the plugins, connect WeChat. But during the week of October 19-25, 2026, the official OpenClaw blog published “Come Build With Us: OpenClaw Focus Weeks” and announced two things: ① the first Focus Week runs on the Control UI, with maintainer Vyctor Brzezowski on point for 7 days; ② the first cohort of rotating Clawtributors is being invited into a shared “OpenClaw Team” environment to work alongside official maintainers. This is not a release. It is a change in governance shape — from “a founder plus a few people writing code” to a three-layer structure of foundation + themed weeks + rotating contributors. The same period shows the Chinese side arriving at collective scale: the “raising lobsters in the pond” public training run jointly by Ningbo’s Haishu District Government Service Center and the District Trade Union drew 90+ enterprises, with roughly 10 sessions planned and 80 public seats per session; the OpenClaw CN community’s “Wildfire Plan” is recruiting the first 100 core contributors.

In one line: the next stage of the lobster is not a bigger version number, it is a question of who builds it and how — contribution shifts from filing pull requests to rotating inside the official environment, and deployment shifts from one person installing software to region-wide collective training and certification.

I. TL;DR — Three Governance-Level Events

#	Layer	Action	Key figure	Date
1	Themed week	First Focus Week, on the Control UI	Oct 19-25, 7 days	October
2	Maintainer	Vyctor Brzezowski as Maintainer on point	Foundation Design Engineer	October
3	Rotation	First Clawtributors into the shared Team environment	Temporary guest access	October
4	UI landings	Batch of Control UI pull requests merged	PR #142143 / #150605 / #165641	Sep-Oct
5	Regression coverage	Focused tests on the UI repairs	162 passing	Sep 8
6	Review rating	ClawSweeper merge readiness	Up to 5/6 “diamond lobster”	Sep-Oct
7	Governance body	OpenClaw Foundation (501(c)(3))	Founded Jul 8, 2026	July
8	Team size	6 engineering + 4 operations	Chief Architect Vincent Koc	July
9	Open roles	Technical, DevRel, design, chief of staff	8 positions	July
10	Community scale	Community contributors with code merged	3,324+	To date
11	Growth	New self-hosted instances per week	4.5 million	July disclosure
12	Events	ClawCon in-person events	34 events / 16 countries / ~30,000 people	Within 5 months
13	China training	Haishu “raising lobsters in the pond” training	90+ enterprises enrolled	2026
14	China program	OpenClaw CN “Wildfire Plan”	First 100 core contributors	Ongoing
15	Derivatives	”Lobster”-derived products on the market	30+	2026

II. Focus Week: How the First Themed Week Actually Works

The official blog post of October 19, “Come Build With Us: OpenClaw Focus Weeks,” describes the mechanism in plain terms: each week the project picks one direction off the OpenClaw roadmap, assigns one maintainer on point, and invites the community to pile in. Every week gets a public community thread where participants compare notes, coordinate effort, and hopefully push a few more things across the finish line.

The first week’s specifics: October 19 through October 25, direction Control UI, with Vyctor Brzezowski as the maintainer on point — per the OpenClaw Foundation people page, he is the foundation’s Design Engineer. The bar for participation is deliberately low: you do not need a polished pull request; “here’s what I tried, here’s what I expected, and here’s what happened” is, in the blog’s words, tremendously useful. The post names concrete starting points: pick up an existing issue, put the web UI through its paces, change a setting, try a fresh setup, navigate with only a keyboard, or find the spot where the workflow forces an unnecessary interpretive dance.

This is not a concept post — it maps to verifiable work on GitHub. Pull requests from Vyctor Brzezowski touching the Control UI clustered densely across September and October: #142143 (merged September 8, five commits, fixing mobile cards that sat out of line with the composer, document previews extending beyond their dialog, and missing keyboard-focus outlines — regression coverage captured at 390 / 768 / 1440 pixels, 162 focused tests passing, production code moving +68 / -55 lines, CI run 34275508520), #150605 (the mobile session filter sheet closing when its heading was tapped), and #165641 (October 5, agent menus become searchable horizontal rows with duplicate-name identifiers and an overlapping inverted stack for three-agent groups). All were reviewed by the ClawSweeper bot, which assigned merge-readiness ratings from “platinum hermit 4/6” up to “diamond lobster 5/6” with P2-to-P3 priorities.

One detail deserves emphasis: the Control UI itself ships 6 locale options — en, zh-CN, zh-TW, pt-BR, de, es. A themed week chosen for the interface rather than the model or a new feature tells you what the project believes its bottleneck is: not capability, but onboarding cost and interaction consistency.

III. Rotating Clawtributors: Bringing the Community Inside the Official Environment

The other half of the blog post, running alongside the themed weeks, is called “More Claws in the Machine.” The project invites a select group of rotating Clawtributors into a shared OpenClaw Team environment with temporary guest access and direct contact with the team.

The key design decision is “building OpenClaw with OpenClaw.” The post says outright that the team wants to see what happens when more people actually use its Team and multiplayer capabilities for genuine collaborative work — what is intuitive, what is clunky, where shared context works as it should and where it leaves somebody wondering what they have stumbled into. The initial group is congratulated and recognized in that week’s Focus Week thread.

The official also draws the boundary explicitly: the Team environment is invite-only for now, but everything else is open to everybody. That line is worth reading twice. What is gated is the privilege of working in the same room as maintainers — not the threshold for contributing. This is the precise sense in which “community building” happens: the depth of contribution is tiered, while ordinary contributors continue to work through public issue and pull-request channels.

IV. Foundation Governance: From One Project to Neutral Stewardship

Themed weeks only survive if there is institutional backing. The OpenClaw Foundation was announced on July 8, 2026 by Dave Morin and Peter Steinberger as a US 501(c)(3) non-profit, with a first full-time staff of 6 engineers (led by Chief Architect Vincent Koc) and 4 operations people (partnerships, finance, community, talent); Morin chairs the board, and 8 positions remain open, including Member of Technical Staff, Forward Deployed Engineer, Product Designer, Head of DevRel, and Chief of Staff.

Structurally, the foundation organizes into three overlapping circles: the full-time team, core maintainers, and community contributors. 3,324+ people have shipped code into OpenClaw, and for many of them it was their first-ever pull request. Core maintainers cluster by employer: NVIDIA 4, Microsoft 4, OpenAI 3, Tencent 3, plus people from Atlassian, Xiaomi, Red Hat, Hugging Face, Paradigm, and others.

Two facts are worth recording. First, OpenAI stood up a Claw Labs team inside OpenAI led by Peter, and is publicly a major donor with an independence commitment; Steinberger’s own formulation is “OpenAI hired me, not OpenClaw. The OpenClaw Foundation is independent, with sponsors rather than owners.” Second, before the foundation, OpenClaw ran at a sustained loss with monthly revenue of only $10,000-$20,000 — unsustainable on donations alone, which is the direct driver behind foundation-ization and corporate sponsorship. The cost side is equally concrete: Steinberger has published $1,305,088.81 of API spend over 30 days (603 billion tokens, 7.6 million requests, roughly 100 Codex instances, a 3-person team), and noted that disabling fast mode makes it “70% cheaper — more like one employee.”

The controversy deserves equal billing. Computerworld consultant Noah Kenney argued that “the ‘neutral steward’s’ chief technical decision maker is employed by one of the competing labs it is supposed to be neutral with.” The security ledger is harder still: OpenSourceMalware identified 386 malicious plugins among more than 3,000 skill packages, and a Moltbook backend misconfiguration leaked roughly 1.5 million API keys and agent-to-agent private messages. Inviting more people into one shared space is precisely what pushes the trust boundary into territory that now has to be governed explicitly.

V. China: From “Personal Pet” to Collective Build

The global side runs on Focus Weeks; the Chinese side runs on a different clock, but points at the same thing: turning “can use” into “can build.”

Ningbo’s Haishu District formally launched its AiOPC community in late December 2025, introducing the NewBoss0574 ecosystem with five coordinated dimensions — space, policy, scenarios, tools, and services — to empower OPCs (one-person companies). The OpenClaw public training is one supporting program: the Haishu District Government Service Center and the District Trade Union jointly ran “raising lobsters in the pond: installation and deployment public training,” which drew 90+ enterprises signing up. Instruction came from Yang Mingfeng, founder of the OpenClaw Chinese community, principal developer of the Chinese edition and a core contributor to the international edition, who is also general manager of Ningbo Yuanzhixingtu Intelligent Technology — and the session included one-on-one deployment guidance on the floor. The fourth session, held April 9, found all 80 public seats taken well before the event, and the series is planned at roughly 10 sessions, moving from understanding the “lobster” to scenario practice and finally to building vertical-domain skill packs.

The payoff is quantified: Yang’s comparison is that handling dozens of invoices plus review and bookkeeping by hand takes a full day, while the AI digital employee “lobster” finishes in 5 to 10 minutes. The March 19 hundred-person bootcamp drew more than a hundred Haishu AiOPC founders, early micro-teams and practitioners; on March 18, Yuanzhixingtu obtained its business license with full walk-through assistance from the district’s “Yuanqi Studio.” LanYu Technology co-founder Li Heng represents a parallel path — a traditional film-and-television firm pivoting to “OpenClaw + industry scenarios” for skills training, project matching and incubation.

The community-side counterpart is the OpenClaw CN “Wildfire Plan,” which openly recruits the first 100 core contributors across three tracks: building connectors for WeCom and DingTalk, testing multi-platform installs and Docker templates, and writing practical Agent tutorials — with an early co-building group and a rate-limit rule that releases one new group QR code per system each night at 8 PM, given thousands of daily joiners.

VI. The Derivative Ecosystem: 30+ Lobsters, and One Underlying Fact

The matrix of products derived from OpenClaw now exceeds 30, each with a distinct strategy: QClaw (Tencent) connects the Agent directly to WeChat and QQ, defaults to Kimi-2.5 and emphasizes local data storage, free during internal testing; AutoClaw (Zhipu) is a local client defaulting to GLM-5/Pony-Alpha-2 with 96 prebuilt skills, AutoGLM browser automation and one-click install; EasyClaw (Cheetah Mobile) takes the “cleaner master” approach and makes the Agent a one-click tool for consumers; MaxClaw (MiniMax) is the cloud-hosted edition, live in 18 seconds from ¥39/month. There are also ArkClaw (ByteDance/Volcano, default Seed 2.0), KimiClaw (Moonshot, memory beyond 1M tokens), WorkBuddy (Tencent), Wukong OpenClaw (Alibaba), JVS Claw, Huawei Claw, Xiaomi MiClaw, iFlytek XunClaw, Baidu DuClaw, and constrained-edge variants such as ZeroClaw (<5MB memory, <10ms startup), PicoClaw (<10MB RAM) and NullClaw (678KB, command line only).

What this list really demonstrates is not how many products exist, but that the upstream project has become a protocol at the bottom of an industry chain. Whoever first defines how agents prove identity, how they are profiled, and how they are evaluated controls the next round of infrastructure discourse — exactly the four council topics the foundation has convened.

VII. FAQ (Frequently Asked Questions)

Q1: How is a Focus Week different from just filing an issue? Difference is density and accountability. An ordinary issue queues into a backlog; a themed week puts one maintainer on that direction full-time for the week and opens a public thread for participants to compare notes and coordinate. The bar is explicitly lowered: no polished pull request needed, a clear reproduction is welcome.

Q2: Can ordinary users join a Focus Week? Yes. The official text is explicit — participating requires no invitation; only the OpenClaw Team environment is invite-only for now, everything else is open to everybody. The first rotating Clawtributors were invited into the Team environment and are recognized in that week’s thread.

Q3: Why did the first Focus Week pick the Control UI? Because the project judges the current bottleneck to be onboarding cost and interaction consistency rather than model capability. The Control UI is the surface every user touches daily and the one where contributors can most easily produce reproducible feedback. The September-October pull request density matches that read.

Q4: What is the relationship between the foundation and OpenAI? Is it neutral? By the official account, OpenAI is a major donor and runs a Claw Labs team inside OpenAI led by Peter for shared product improvements; Steinberger’s phrasing is “OpenAI hired me, not OpenClaw.” Neutrality is publicly contested, though: a Computerworld commentator argues the neutral steward’s chief technical decision maker is employed by a competing lab. Both facts should be stated side by side.

Q5: What does “community building” concretely look like in China? Two tracks. One is regional public service — Ningbo’s Haishu District, with the government service center and trade union co-hosting public training: 90+ enterprises enrolled, roughly 10 sessions, 80 public seats each, aimed at turning “keeping a lobster” into a repeatable organizational capability. The other is developer supply — the OpenClaw CN “Wildfire Plan” recruiting the first 100 core contributors to fill in connector plugins for WeCom, DingTalk and other mainstream Chinese apps.

Q6: Will derivative products replace the original? Not by current design intent. Most packaged products lock the default model — QClaw defaults to Kimi-2.5, MaxClaw to MiniMax’s own M2.5/M2.7 — while the original and alternatives such as AutoClaw and WorkBuddy support switching models freely, which keeps the original the rational choice for users who need model optionality.

Q7: How is security risk managed as the community expands? That is the core tension between the foundation and the shared Team environment. Public figures so far: 386 malicious plugins identified among more than 3,000 skill packages, roughly 1.5 million API keys leaked in the Moltbook incident, and a one-click account takeover vulnerability that was found in under two hours. Foundation investment in hardening (Microsoft’s upstream security contributions, Tencent’s dedicated security and stability maintainers) and community expansion are two sides of one coin.

VIII. Key Terminology

Focus Week: A week-level collaboration mechanism in OpenClaw — each week selects one roadmap direction, assigns one maintainer on point, and opens a public community thread for global participants to compare notes and coordinate. The first ran October 19-25 on the Control UI.

Maintainer on point: The maintainer holding final technical responsibility for a given direction during that themed week. Vyctor Brzezowski held it for the first one.

Clawtributor: A nickname for community members who contribute code to OpenClaw, blending claw and contributor. More than 3,324 people have merged code; for some it was their first pull request ever.

OpenClaw Team environment: A multiplayer shared workspace where different people and their agents work through sessions in one environment, share context, and pick up where someone else left off — even letting pull requests carry the conversation context that produced them. Currently invite-only.

Rotating: The first Clawtributors receive temporary guest access and a direct line to the team, participating on a rotating basis rather than becoming employees or permanent members.

ClawSweeper: OpenClaw’s automated review bot, which issues merge-readiness ratings on pull requests (a hermit/lobster tier system, such as platinum hermit 4/6 and diamond lobster 5/6) and P0-to-P3 priority recommendations.

501(c)(3) non-profit foundation: A US tax-exempt organizational form under the Internal Revenue Code. The OpenClaw Foundation was established in this form on July 8, 2026, with Dave Morin as chairperson, explicitly modeled on the governance of Linux, Apache and Mozilla.

AiOPC community / “raising lobsters in the pond”: Haishu District’s community-incubation system for one-person companies, launched in late December 2025 with five coordinated dimensions — space, policy, scenarios, tools and services. “Raising lobsters in the pond” is the public training brand built on OpenClaw underneath it.

IX. References

Official sources

OpenClaw official blog, “Come Build With Us: OpenClaw Focus Weeks” (Oct 19, 2026 — first themed week Oct 19-25, Control UI, maintainer Vyctor Brzezowski, author Joe Pishgar)
OpenClaw Foundation people page, openclaw.org/people (full-time staff roster including Chief Architect Vincent Koc, Design Engineer Vyctor Brzezowski, Community & DevRel Joe Pishgar, Chairperson Dave Morin; 3,324+ community contributors)
OpenClaw Foundation launch announcement (Jul 8, 2026 — 501(c)(3), co-signed by Dave Morin and Peter Steinberger, 6 engineering + 4 operations staff, 8 open positions)
openclaw.ai homepage statement on independence (OpenClaw is a donor-backed model, not an OpenAI product)

Code and collaboration records

GitHub openclaw/openclaw PR #142143, “fix(ui): align mobile cards, contain previews, and restore focus outlines” (merged Sep 8, 2026 — 162 focused tests, CI 34275508520)
GitHub openclaw/openclaw PR #150605 / Issue #160600 (mobile session filter sheet dismissal bug)
GitHub openclaw/openclaw PR #165641, “improve(ui): make agent menus easier to scan” (Oct 5, 2026 — searchable horizontal rows, duplicate-name identifiers, overlapping avatar stack)
GitHub openclaw/openclaw Issue #151489, “Control UI: consolidate icon buttons” (opened Sep 18, 2026)

China-side deployment

Ningbo Haishu District Government, “Haishu District AiOPC maker cultivation public training opens, unlocking OpenClaw technology for enterprise digitalization” (the “raising lobsters in the pond” installation and deployment session drew 90+ enterprises, taught by Yang Mingfeng with on-site one-on-one deployment guidance)
Ningbo Haishu District Government, “‘Cultivation-style’ lobsters, taught step by step in Haishu” (Mar 19 hundred-person bootcamp; Mar 18 business license for Yuanzhixingtu; LanYu Technology’s Li Heng on the pivot)
Ningbo Trade Union Network, “Every seat taken: this Haishu AI training brought the ‘digital employee’ home” (fourth session Apr 9 — 80 public seats gone early, roughly ten sessions planned, invoice review and bookkeeping compressed from a full day to 5-10 minutes)
China National Radio, “Unlocking new momentum for AI entrepreneurship — Ningbo Haishu District AiOPC community holds OpenClaw deployment practical camp” (Haishu district talent office: bootcamps and an OpenClaw application innovation competition to follow)
OpenClaw CN community site (MulanOS open-source community) — “become a core contributor” and “join the Wildfire Plan” pages (first 100 core contributors; one group QR code released per system per day at 8 PM)

Ecosystem and third-party observation

AI Bot Box, “OpenClaw Orange Paper” derivative product survey (as of Mar 11, 2026, at least 10+ products available; MaxClaw from ¥39/month with 18-second deployment; AutoClaw with 96 prebuilt skills; QClaw defaulting to Kimi-2.5)
CSDN, “OpenClaw community resources and future roadmap — skill marketplace, contributor ecosystem and commercialization” (positioning table for the QClaw / AutoClaw / EasyClaw / MaxClaw derivative ecosystem)
ExplainX, “OpenClaw Foundation: 501(c)(3) Non-Profit, Full-Time Team, Major Partners” (4.5M new claws per week; ClawCon — 34 events, 16 countries, ~30,000 signups in five months; partner and donor breakdown)
Tencent News, “‘The Switzerland of AI’: OpenClaw officially transitions to a non-profit foundation” (maintainer composition: NVIDIA 4, Microsoft 4, OpenAI 3, Tencent 3; security incidents: 386 malicious plugins among 3,000+ skills, ~1.5M Moltbook keys leaked)
AI Wiki, “Peter Steinberger” (Claw Labs established inside OpenAI; $1.305M API spend over 30 days / 603B tokens / 7.6M requests / ~100 Codex instances; OpenClaw Enterprise donated to the foundation on Sep 29)