Cloned a Grok Bot the week it launched and got 10K stars: CopilotKit's OpenBot and the "Open + original name" playbook behind it
What it is A self-hosted AI coworker platform: each bot gets its own browser and file system, every action is checked against rules and logged, and it works with any agent framework and any model.
Why it took off After xAI's Grok Bot blew up in August, it shipped an open-source version within 6 days and claimed the "open-source Grok Bot" spot. In late October, Grok Bot leaked user data and got rate-limited, and people who wanted an alternative came looking. OpenBot hit #4 on GitHub's daily trending list, and trending and repost sites amplified it again.
CHow you can apply this Stop cloning Grok Bots. The next time a big lab launches a hit agent product, ship an "Open + original name" open-source version within a week, runnable with one command, and only target the original's biggest structural weakness (runs locally, swappable models, your data stays yours). When the original has an incident, publish a comparison and a migration guide.
- Data (updated daily) · Repo created 2026-08-17 · 10,385 stars · 7 days +1,263
GitHub · stars Data 2026-08-26 → 2026-11-08 (75 days, 33 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
OpenBot is an open-source, self-hostable "Grok Bot." It hit 10,240 stars in 81 days, and gained 661 stars in a single day in October 31. It rode two waves of interest: the original product launched in August, and OpenBot shipped an open-source version within 6 days. Then in late October the original got into trouble and was rate-limited, users went looking for alternatives, and OpenBot gained another surge. It isn't built by an indie dev but by a company that just raised a $27M Series A and has a main repo with 38K stars. Devs chasing stars can learn a repeatable playbook from it, but the "open-source Grok Bot" spot is already crowded.
eight days after the original launched
In 2026 Aug 11, xAI released an early beta of Grok Bot: an AI coworker with its own computer that can open browsers, click through websites, and handle files. The official tweet got 36K likes, and it scored 351 points on Hacker News.
On Aug 17, CopilotKit created a GitHub repo called OpenBot. On Aug 19, CEO Atai Barkai (7K followers on X) posted:
Introducing Open Bot. An open source Grok Bot that works with ANY agent harness, designed for real companies.
Replies listed five points: an AI coworker, generative UI, controlling a computer locally or remotely, handoff between agent and human, and all data logged and owned by you. The tweet got 3,046 likes and 848K views, and was bookmarked 4,516 times, more than it got likes, suggesting many people saved it to use later. The next day an angel investor reshared it, saying they had "open-sourced a Grok Bot within hours of the original launch." The same-day Show HN got only 12 points, and Hacker News didn't help much.
On Sep 1, the official blog said it had passed 3,500 stars.
What it is
A self-hosted AI coworker platform. Each bot gets its own container computer, with its own Chromium, login state, and files, isolated from each other. A gateway checks every action the bot takes on the computer, files, or tools against rules before it runs, and writes it to an audit log. When the bot shouldn't act on its own, a human can take the wheel and hand control back when done. Any agent that follows the AG-UI protocol (the agent frontend protocol CopilotKit leads) can plug in, whether it's built on LangGraph, Mastra, CrewAI, or hand-rolled, and you choose the model.
Compared with the original, there are three differences: Grok Bot runs on xAI's cloud, all of a person's bots share one computer, and you can't change models. OpenBot runs on your own machine, each bot gets its own computer, and you choose the model and framework.
The first line of the README says "A template, not a product": there's no hosted version and no npm package. You clone the whole repo and modify it into your own. Running it requires Docker, Bun, and a CopilotKit Intelligence license (there's a free tier). So far fewer people likely deploy it than star it (my inference).
How the stars grew
| Date | Stars | What happened |
|---|---|---|
| 08-17 | 0 | Repo created, day 6 after Grok Bot launched |
| 09-01 | 3,500 | official blog announces |
| 10-17 | 6,553 | day 60, eligible for GitHub trending |
| 10-28 | 7,472 | +289 that day, second wave begins |
| 10-31 | 8,654 | +661 in a single day, #4 on the overall daily chart |
| 11-03 | 9,880 | +454 that day |
| 11-06 | 10,240 | daily gains fall back to around 120 |
GitHub stars, daily data available from 10-17; the last 7 days +2,247, which is 2.2 times the previous 7 days.
The first wave was about timing. The repo was created 6 days after the original launched, named Open + Bot, and the CEO and the official account posted the same day. People had just been wowed by Grok Bot, and searching "open source Grok Bot" put it in the first results.
The second wave wasn't self-inflicted. In Oct 19, Techdirt reported that a Grok Bot leaked a tech CEO's bank details in a public Slack channel. By late Oct, many users had run out of their weekly quota early. In Nov 1, Musk admitted the service's cost was "unsustainable" relative to its revenue. In Nov 2, TechCrunch and The Verge both wrote about the "rate limits." Leaks, caps, and no way to swap the model: that hits right at OpenBot's pitch. Your data stays on your own server, every action is approved and logged, and you bring your own model key, so no quota limits.
The clearest sign is that similar projects rose together: nightly-labs/openbot, with the same name, went from 10-26 to 11-06, a 6.9x increase, and OpenMausBot, an individual developer's project, gained 5,800 stars over 7 days starting from 10-28, outpacing OpenBot. The inflection happened on the same day, which means users who wanted to replace Grok Bot went looking together. OpenBot didn't do anything special on its own.
Trending feeds itself. GitHub Trending only lists repos about 60 days old, and OpenBot's Oct 16 was right on that line. On Oct 30 it hit the site-wide daily chart for the first time (#9), and ran from 31 through #4. In the three or four days after it charted, a batch of auto-repost sites and "today's recommended repos" blogs picked it up, and Facebook, Instagram and LinkedIn filled with reposted videos titled "Someone just open-sourced an AI coworker that gets its own computer," while YouTube had one called "The Free Grok Bot Alternative Nobody's Talking About." Whether this spread on its own or was paid for, I haven't verified. The README then got a Trendshift "#3 Repository Of The Day" badge at the top.
It kept working in the meantime. On October 22 and 23, the official account published a batch of comparison pages in quick succession: "OpenBot vs Grok Bot," "vs OpenAI dots," "vs Meta Muse," and "vs Hermes Agent," aimed at "X alternative" searches. It also ran an online enterprise webinar with about 11K views on YouTube. Over two and a half months it shipped 21 releases and about 700 commits, a pace that's hard for one person to match.
It wasn't a one-time copy
The same team used the same formula to build a whole lineup: OpenTag (modeled on Claude Tag, 1.3K stars), OpenBot, openmuse (modeled on Meta Muse, 6.2K), OpenDots (modeled on OpenAI dots, 6.4K), and OpenDuet (modeled on Claude Duet, 2.0K). The official account said in October that these added up to over 19K stars and "millions of views." Apart from OpenTag, each one passed several thousand stars.
The formula: a big lab launches a hit agent product, an open-source version ships within a week, the name piggybacks on the original, the selling point targets a weakness the original structurally can't fix (data not in your hands, no audit, locked to one model vendor), then you wait for the original to have an incident.
For CopilotKit, these repos are for customer acquisition. The first buttons at the top of the README are "Talk to an engineer" and "Have us build it with you," and the enterprise version sells engineers who come in to deploy it. These articles don't talk about money, though. For you as someone thinking about open source, the takeaway is that this formula reliably brought in stars.
Who it's competing with
| Project | Stars | How OpenBot differs |
|---|---|---|
| Grok Bot (xAI, the original) | Closed source; paid weekly actives around 800K in October (per teslarati, citing company data) | Cloud-hosted, one shared computer per person, no model choice |
| milind-soni/OpenMausBot | 13.1k, +7k in the last 5.8 days | Repo created the day the original launched; aimed at individuals, uses your existing Claude, Codex, or Grok subscriptions; the most stars in this category |
| elie222/rakazo | 7.2k | Aimed at individuals and developers, you choose the model and sandbox; ranked first on open-source alternative lists |
| nightly-labs/openbot | 5.8K, up 6.9x from 10-26 | Same name, a local-first desktop app with multi-user collaboration; many articles and videos mix the two up |
| leepokai/Codync | 1.9k | Plugs into your existing Claude Code and Codex subscriptions |
| gawkbot, rome, AnyModelBot, rerun, and others | Varies | all "open-source Grok Bots" |
Star counts from GitHub, 11-06.
There are at least ten "open-source Grok Bots," and the one with the most stars is OpenMausBot, from an individual developer. OpenBot is second, and it's the only one here that clearly targets enterprise use, with audit and no framework lock-in.
If it were you
Verdict: C. Building another "open-source Grok Bot" today means competing for the same search term against a dozen-plus projects with thousands to tens of thousands of stars, and the second wave of demand is fading too (daily gains dropped from 661 to 120). The part worth taking is the playbook: next time a big lab launches a hit agent product, ship an open-source version in the first week. OpenMausBot shows this works for individuals too. It was created the day the original launched, and now has more stars than OpenBot.
Who it suits: developers who move fast and can build a working demo in a few days, who already watch big-lab AI product launches, and who have some X following or an existing starred repo to funnel people from.
Who it doesn't suit: people who want to slowly polish a large all-in-one platform (OpenBot is backed by a funded team that shipped 21 releases in two and a half months), and anyone hoping to squeeze into the Grok Bot alternatives category now.
How to do it: ① Watch big-lab launches (new agent features from xAI, OpenAI, Anthropic, Meta, Google), and create the repo within 1 to 7 days of launch, named Open + the original's name; ② Target only one structural weakness of the original, like running locally, swapping models, keeping data yourself, or having an audit log, rather than trying to cover everything; ③ Make it runnable with one command. OpenBot needs Docker, Bun, and a license key, and that's where it fell short, which is where a solo project can win; ④ The week the original has an outage, a price hike, or rate limits, immediately publish a "vs original" comparison and migration guide.
How to get users: On launch day, post on X with a demo video, stating clearly "open source X, works with any X." A Show HN is fine, but don't count on it. Once you've been on trending for 60 days, save the second push for later (a major version update, a comparison post). Put the trending badge at the top of the README.
When to move: For the next original, it's within the first week after launch. After the first week, same-name and similar repos fill up the term. For the Grok Bot category, that window has already closed.
Signs this read is wrong: ① New "open-source Grok Bots" built from scratch reach several thousand stars after November, which would mean the category isn't saturated yet; ② The open-source versions shipped in the first week of the next big-lab agent launch mostly fail to reach a thousand stars, meaning the "Open + original name" playbook is worn out; ③ OpenBot keeps adding a hundred or two a day in months when Grok Bot has no incidents, meaning its enterprise positioning is pulling in users on its own, not just riding the original's heat.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one Grok Bot(xAI) Big-company features 2026-08-11 October paid weekly actives around 800K, DAU 600K+ (teslarati) The original is cloud-hosted, one shared computer per person, can't be self-hosted, and has no model choice; OpenBot is self-hosted, with a dedicated computer per bot and any model or agent milind-soni/OpenMausBot Open source 2026-08-11 13.1K stars, +5.8K in the last 7 days Aimed at individuals, uses existing subscriptions; OpenBot is aimed at enterprises, with a governance gateway and SSO elie222/rakazo Open source 2026-08-13 7.2k stars For individuals/devs: pick a model and sandbox, no audit or governance layer nightly-labs/openbot(openbot.run) Open source 2026-08-12 5.8k stars, up 10/26 6.9x; PH 10/7 Same name, local desktop app + multiplayer collab; OpenBot is a server-side template deployable to K8s leepokai/Codync Open source 2026-03 1.9k stars Personal tool that plugs into your Claude Code/Codex subscription OpenAI dots / Meta Muse / Claude Duet Big-company features 2026 Not verified Hosted personal agent; CopilotKit shipped an open-source clone of each - Where users come from
- Verified Riding the original launch + name piggybacking: Grok Bot launched 08-11, OpenBot repo created 08-17; an investor tweeted that it open-sourced Grok Bot hours after the original (x-radar)
- Verified X (founder/official accounts): CEO @ataiiam posted the launch tweet 08-19 with 3,046 likes; @ClaudeDevs posted an AG-UI cookbook 08-20 with 2,349 likes (x-radar)
- Verified Show HN: the 08-19 Show HN post got only 12 points (hackernews database)
- Verified Platform events (Grok Bot leak + rate limits): 10/19 Techdirt leak incident; 11/01 Musk admitted costs were unsustainable, covered by TechCrunch/Verge 11/02; in the same period OpenMausBot, nightly-labs/openbot and Codync all surged (github database)
- Verified GitHub trending flywheel and reposts: 10/30 entered the site-wide daily trending, peaking at #4 10/31; 10/29–11/01 multiple repost sites/blogs picked it up (Exa)
- Verified SEO comparison pages + webinar: 10/22–23 published vs Grok Bot/dots/Muse/Hermes comparison pages; a YouTube webinar got about 11k views
- Inferred Short video / social reposting: FB/IG/LinkedIn videos titled "Someone just open-sourced an AI coworker", YouTube "Nobody's Talking About", Reddit threads; whether paid promotion was run is unverified
CopilotKit/OpenBot: why it took off
Research date 2026-11-06. Sources: our github / hackernews / producthunt databases, x-radar, GitHub API, Jina/Exa web search. Figures are sourced inline.
Bottom line
OpenBot is CopilotKit's (Seattle, 2026-05 just raised a $27M Series A) open-source, self-hosted "Grok Bot" that works with any AG-UI agent, shipped days after xAI's Grok Bot went viral. It grew in two waves: the first (late August to 3.5k stars) rode the Grok Bot launch buzz, with the CEO pushing it on X and a Show HN post; the second (10/28, up 2.2k stars in a week) was a platform event. Grok Bot was suddenly rate-limited in late October, and 10/20 had a leak, so the whole "open-source Grok Bot alternative" category spiked at once. OpenBot hit GitHub's global trending from 10/30 (peaking at #4), and trending fed on itself. The product's edge (a separate computer per bot, every action approved before it runs and logged, no framework lock-in) is why companies and developers pick it over the other clones, but it isn't why it blew up. Really, it's CopilotKit's lead funnel: the README and website are all "Talk to an engineer / let us build it for you," and the money comes back through OpenBot for Business (on-site engineer deployments) and CopilotKit Intelligence licenses.
1. Basic data
- Repo created 2026-08-17, MIT, TypeScript, about 700 commits (GitHub API), releases v0.0.1(08-17) → v0.3.1(11-06), 21 tags total.
- Stars: 9/1 The official blog said it passed 3,500 stars (copilotkit.ai/blog/openbot-updates-v0.0.5); 10/17 6,553; 10/28 7,472; 11/06 10,240 (github database repo_day); the GitHub API live that day showed 10,312.
- Last 7 days +2,247, first 7 days +1,015; single-day peak +661 at 10/31 (github database). 10/28–11/03 daily roughly +289/+201/+320/+661/+468/+304/+454,11/04, then cooled to about +120/day.
- Trending (github database): 10/23 TypeScript chart #15; 10/30 first entered the site-wide daily chart at #9,10/31 overall, #4 overall and #3 in TS; 11/01–11/06 ranked #5–7 on the TS weekly chart for consecutive days. Note trending only includes repos about 60 days old, and OpenBot only reached 10/16 days by 60, so not charting earlier doesn't mean it wasn't hot.
- Same org (github database): CopilotKit main repo 38.5k; sister repos using the same playbook: OpenDots 6.4k (clone of OpenAI dots), openmuse 6.2k (clone of Meta Muse), OpenDuet 2.0k (clone of Claude Duet), OpenTag 1.3k (clone of Claude Tag). The official claim is that these total 19k+ stars and "million-scale views" (copilotkit.ai/blog/introducing-soar, 10/22).
2. Competitors
There are many originals being copied and many open-source alternatives; "open-source Grok Bot" is itself a crowded lane since late August 2026.
| Name | Where | Launched | Scale | How it differs from OpenBot |
|---|---|---|---|---|
| Grok Bot(xAI/SpaceXAI) | Big-tech features (web/desktop/iOS/Android) | 2026-08-11 early beta (@bot tweet 36k likes; HN 351 points) | October paid weekly actives around 800k, DAU 600k+ (teslarati citing company data) | Hosted in the cloud, one shared cloud computer per person, models not selectable, no local deployment; OpenBot is a self-hosted template with an independent computer per bot and any model or agent |
| milind-soni/OpenMausBot | Open source | 2026-08-11 | 13.1k stars, +5,817 in the last 7 days (github database) | Same "open-source Grok Bot + VM" idea, but aimed at personal use and runs on the Claude/Codex/Grok subscriptions you already have; its growth has been even faster than OpenBot's |
| elie222/rakazo | Open source | 2026-08-13 | 7.2k stars (github database) | Aimed at individuals/devs, pick model and sandbox; ranked #1 on the opensourcealternatives.to list |
| nightly-labs/openbot(openbot.run) | Open source + desktop app | 2026-08-12 | 5.8k stars, rose from 839 to 5,773 starting 10/26 (github database); was on Product Hunt 10/7 | Same name, local-first desktop workspace with multiplayer collab; third-party articles/videos often confuse the two |
| leepokai/Codync | Open source | 2026-03 | 1.9k stars | Plugs into your existing Claude Code/Codex subscription, personal focus |
| OpenAI dots / Meta Muse / Claude Duet | Big-company features | 2026 years | Not verified | Similar hosted AI coworkers; CopilotKit also shipped open-source clones of each of them |
| rowboatlabs/rowboat, Anil-matcha/open-dots, open-duet, etc. | Open source | 2025–2026 | 5–18k stars | General-purpose AI coworker / multi-agent workspace, without the governance gateway layer |
Bottom line: it's not that there are no competitors, it's that they cluster. OpenBot's star count ranks second among "open-source Grok Bot" projects (behind only OpenMausBot), but it's the only one that explicitly targets "enterprise + governance audit + no framework lock-in."
3. Growth tactics (evidence)
- Riding the original launch, cloned at speed: Grok Bot launched 08-11, OpenBot repo created 08-17; angel investor Joe Heitzeberg tweeted 08-20 that it "open source'd Grok Bot hours after the original" (x-radar). CEO Atai Barkai (@ataiiam, 7k followers) posted 08-19 "Introducing Open Bot — an open source Grok Bot that works with ANY agent harness," getting 3,046 likes (x-radar); the official @CopilotKit account posted at the same time. The name, "Open + Bot," directly piggybacks on the original.
- Show HN: the 08-19 post "Show HN: Open Bot – an open-source Grok Bot that works with any agent harness" got only 12 points (hackernews database). HN was not the main channel.
- Org-owned traffic + ecosystem backing: CopilotKit's main repo has 38k stars, and the AG-UI protocol has been adopted by Google/Microsoft/Amazon/Oracle; 08-20 @ClaudeDevs (690k followers) posted an AG-UI × Claude Managed Agents cookbook (x-radar, 2,349 likes), plus a sponsorship of LangChain Interrupt NYC (x-radar).
- Assembly-line content/SEO: a "passes 3,500 stars" blog post 9/1; 10/22 OpenBot for Business launch + YouTube webinar (channel page shows 11k views); 10/22–23 a burst of "OpenBot vs Grok Bot / vs OpenAI dots / vs Meta Muse / vs Hermes Agent" comparison pages, capturing "X alternative" search traffic.
- Platform event (the main driver of the second growth phase): 10/19 Techdirt's "Grok Bot leaked tech CEO bank data in a public Slack" (HN 36 points); at the end of October, users hit their weekly quota early, 11/01 Musk admitted "service costs are unsustainable relative to revenue," and 11/02 TechCrunch, The Verge, the Independent and others piled on with coverage of "rate limits" and a "rug pull." The whole category surged at the same time: nightly-labs/openbot went from 10/26 to 11/06, up 6.9x; OpenMausBot gained 5.8k over 7 days starting 10/28; Codync accelerated clearly starting 10/28 (GitHub repo data). OpenBot's inflection point starting 10/28 lines up exactly with these, which points to a demand-side event driving it, not anything OpenBot did itself.
- Trending flywheel + secondary distribution: after 10/30 entered site-wide trending, a batch of automated/semi-automated repost sites and blogs appeared between 10/29 and 11/01 (trend.ondo.sh, hdatf.com, runany.dev, freshweights, thetesserapress, jorgeturbica's "Repo of the day," devtoolwatch, programnotes reposting from PH, etc., per Exa search). The README header also carries a Trendshift "#3 Repository Of The Day" badge.
- Short video / social reposting: on Facebook/Instagram/LinkedIn there are reposted videos along the lines of "Someone just open-sourced an AI coworker that gets its own computer," a YouTube video "The Free Grok Bot Alternative Nobody's Talking About," and Reddit posts in r/SelfHostedAI and r/BestGitHubRepos (Jina search). View counts and posting dates are unverified, and whether the official side ran paid promotion is unverified.
- No ad library hits found (the ad libraries only track listed products, so this doesn't mean no ads were run).
4. Why it took off
- Timing: Grok Bot was one of the fastest-growing AI products of the second half of 2026 (Musk called it the "fastest growth ever"). It taught everyone the category of "an AI coworker with its own computer" overnight, which created searches and demand for "open-source / self-hosted versions"; OpenBot claimed that keyword within 6 days.
- Platform mishap amplifies demand: Grok Bot's leak incident and the October rate limits hit exactly where OpenBot sells (data stays on your own server, every action has approval and audit, your own model key with no limits), bringing a second wave.
- Resources: A $27M Series A team, a 38k-star main repo, and AG-UI ecosystem backing give it distribution and credibility from day one. 700 commits and 21 releases in two and a half months, an iteration pace no solo project can match.
- A repeatable play: The same team ran the formula on OpenTag→OpenBot→OpenMuse→OpenDots→OpenDuet. Every one except OpenTag hit thousands of stars, which makes it a systematic "open-source clone of a hot closed product" acquisition strategy, not luck.
5. Differentiation, and whether it was the reason for the growth
- Differentiation: ① each bot gets its own isolated container computer (Chromium, login state, files separated), versus Grok Bot where one person's bots share one machine; ② every action goes through one gateway that decides by policy first and writes audit after, with "take the wheel" for human takeover; ③ it connects to any framework's agent via AG-UI (LangGraph/Mastra/CrewAI/ADK…) and isn't tied to a model; ④ generative UI replies; ⑤ enterprise SSO/SCIM/Helm deployment.
- My read: differentiation is not why it grew. Both waves were driven by the Grok Bot events, and other repos in the category grew at the same time (OpenMausBot grew even faster). The differentiation's job is to position it as the enterprise version in its category, turning stars into "Talk to an engineer" leads. Its README itself says "A template, not a product," with no hosted version and no npm package, so real usage is very likely far below the star count.
6. Visibility and copycats
- Visibility: it's circulating in small circles, but with some real reach. Developer media and many reposting sites covered it, and it hit #4 on the site-wide trending list. But mainstream tech press covered the Grok Bot rate limits themselves, not OpenBot specifically. No public revenue (it isn't a direct paid product).
- Copycats: the space was already crowded, with at least 10 open-source "Grok Bot" alternatives (OpenMausBot, rakazo, nightly-labs/openbot, Codync, gawkbot, rome, AnyModelBot, rerun, etc.). Anil-matcha and others are also using the same "open-X" play to clone dots/Duet.
7. Takeaways
- After a big company launches a hit agent product, an open-source/self-hosted version appears within a week, with the name directly tied to the original (Open + original product name). The CEO tweets the same day, then publishes a "vs the original" comparison page to capture substitute searches.
- They pick selling points that expose the original's structural weaknesses (data sovereignty, audit, model lock-in), so when the original has an incident, a price hike, or rate limits, migration traffic comes naturally.
- Open source is just the funnel: a "book an engineer" CTA sits at the top of the README, converting into on-site deployment services.
- A repo only qualifies for trending after 60 days, so the second push should be timed for 60 days later.
8. Uncertain
- The day-by-day star curve for the August first wave (the stargazer API was unavailable, so only the official 9/1 3,500 data point).
- Whether the social-media repost videos are organic spread or CopilotKit paid promotion / creator outreach.
- Actual deployment numbers and how many paying customers OpenBot for Business has: unknown.
- A notable share of third-party content refers to the similarly named nightly-labs/openbot, so citations need to distinguish them.