· Updated · 11 min read · Omkar Satpute and Milind Soni
OpenMuse vs MausBot: every open source Muse, compared
CopilotKit’s OpenMuse, now OpenFuse, and nanoMuse, which began as OpenMuse, are the open source Muse projects that matter. How each compares with MausBot.
OpenMuse is a name, not a project, and MausBot is the app. Several GitHub repositories took the name after Meta launched Muse on September 8, 2026. Two matter, and both have moved since October. CopilotKit’s OpenMuse, renamed OpenFuse on November 13 (6,484 stars on November 15, MIT), is a phone-first alpha template that needs CopilotKit’s Intelligence service and does not operate your own computer. nanoMuse (3,499 stars, GPL), which began life as OpenMuse, reached version 1.0.9 with apps for phone and desktop and screen-driven hands that its own roadmap says fail on grounding. Both are one agent. MausBot is one team of the AI agents you already have, on your own machine, Apache 2.0.
What “open muse” means on GitHub
Meta’s Muse is a single proactive agent in an isolated cloud virtual machine, on iOS, Android, the web, WhatsApp and, since September 17, a Mac app, free with a usage meter and paid tiers at $20 and $100, in the US, Canada, Japan and Singapore. Nat Friedman, head of product at Meta Superintelligence Labs, said Muse was “definitely heavily inspired as a product by OpenClaw”, and TechCrunch reported that it copied the exact file names of OpenClaw’s workspace. The open source response was immediate and scattered. Here are the four with code worth reading, from their own repositories, first read on October 8 and read again on November 15, 2026.
OpenMuse, by CopilotKit, now OpenFuse
CopilotKit/openfuse launched as CopilotKit/openmuse on September 22 with a tweet seen about 1.17 million times by November 15, and on November 13 CopilotKit renamed it OpenFuse; the old address redirects. It is a monorepo: an Expo app for iOS, Android and web, a Hono API with a task worker, a Playwright Chromium worker, and an optional Linux workspace in its own container, deployable to Render as three services. It has durable task plans with saved receipts, a stored review before every send or calendar change, goals, page watches, finance summaries and “Ideas”. The README is candid: “Alpha, for self-hosting and building on”, its demos use fictional data, and every mode needs a CopilotKit Intelligence project key, because “Intelligence is a separate service and is not included in this repository’s MIT license”. An open issue, filed September 26, asks to make that optional. Telemetry defaults to full capture. The agent browses public pages and runs commands in its own container; another open issue asks for it to “click, type and fill forms on web pages”, graphical desktops are listed as future work, and it has no way to touch the apps on your Mac or PC. No app binaries are produced; models come from OpenAI, Anthropic or Google API keys. It is the best-engineered template in this group and a developer’s starting point.
nanoMuse
nano-muse/nanoMuse began life as OpenMuseAgent/OpenMuse and was renamed. It is the most product-like of the clones, and it has grown up since October: 3,499 stars on November 15, fifty releases since September 25, version 1.0.0 on October 9 and 1.0.9 on October 29. It ships an Android APK, an iPhone and iPad TestFlight beta, Mac builds that are not notarized, a Windows EXE that asks you to click Run anyway, and Linux builds. Each device runs its own agent, an Alpine Linux under proot inside the phone app and DeepSeek Harness on the desktop, with screenshot-driven “hands” that operate apps on Android and on desktop screens, a stop before deleting, sending or paying, Markdown memory files, routines that run while the app is closed, a morning feed, twenty-six model providers plus ChatGPT, Claude and Kimi plan sign-in, and a free model allowance on a community relay. It uses no third-party analytics, though signed-in conversations sync to its relay by default. Its Show HN had drawn 68 points and 21 comments by November 15, and there is an arXiv paper by researchers at Zhejiang University. The roadmap is candid: the hands “fail on grounding” and on recovery after an unexpected dialog, and voice is input only. It is GPL-3.0, not Apache, which matters if you want to build on it.
Digger’s openmuse and chyroc’s open-muse
diggerhq/openmuse was first to the name, created on September 10: a web app on OpenComputer Serverless Agents, with 54 stars, no license file and no commit since September 11. chyroc/open-muse is an iPhone and Mac client for Volcano Engine’s Ark Managed Agents, with Claude Managed Agents as an alternative backend. Since October it has gained an MIT license; it has 124 stars, a signed and notarized Mac app with real Mac computer use behind an allow once or allow for this chat choice and blocked apps and folders, Apple Health and Calendar, and a Quick Chat overlay.
OpenMuse vs MausBot, side by side
| OpenFuse (was CopilotKit OpenMuse) | nanoMuse | MausBot | |
|---|---|---|---|
| Made by | CopilotKit, a VC-backed company | Researchers at Zhejiang University, per its arXiv paper; site nanomuse.cn | Supamaus, an independent open source project |
| Launched | Repository created September 15, 2026; announced September 22; renamed OpenFuse November 13 | First release September 25, 2026 | First commit August 12, 2026, as OpenGrokBot |
| Stars, forks (Nov 15, 2026) | 6,484, 952 | 3,499, 419 | About 23,000, 3,196 |
| License | MIT, but every mode needs a CopilotKit Intelligence key, a separate service outside the license | GPL-3.0-or-later | Apache 2.0, apart from an enterprise/ folder |
| Status | Alpha, for self-hosting and building on; demos use fictional data | Version 1.0.9, after fifty releases; 1.0.0 shipped October 9 | Desktop and phone apps out; Cloud plans live |
| Shape | One agent: an Expo app for iOS, Android and web over a Hono server, a Playwright browser worker and an optional Linux workspace | One agent per device: phone app, desktop app, web console and a relay, all in one repository | A team of bots in a desktop app, with iPhone and Android apps |
| Installers | None; a Deploy to Render button for the server | Android APK, iPhone TestFlight beta, Mac builds not notarized, a Windows EXE that needs Run anyway, Linux builds | macOS, Windows and Ubuntu installers, the Windows one not code-signed yet; iPhone and Android apps |
| Models | OpenAI, Anthropic or Google by API key | Twenty-six providers, or ChatGPT, Claude and Kimi plan sign-in; a free relay allowance | 16 agent engines (Claude Code, Codex, Grok and more), API and local models, chosen per bot |
| Controls your own computer | No; its own browser and container only. An open issue asks for it to click, type and fill forms at all | Yes, by screenshots, on Android and desktop; the roadmap says the hands fail on grounding | Yes: bots run on your own computer, can use your own Chrome, or get a cloud computer with a live desktop |
| Before it acts | Every send or calendar change requires its own stored review; you can take over the browser | A stop before deleting, sending or paying, remembered for once, this chat or always | Full access by default, or Ask, Auto-accept edits or Approve for me per bot; sends can be set to ask every time |
| Memory | Editable name, tone, avatar and memories | SOUL.md, USER.md, MEMORY.md and HEARTBEAT.md you can read and edit | Editable Markdown notes per bot, plus an About me every bot reads |
| Proactive | Ideas, goals and page watches | Goals on a schedule, routines while the app is closed, a morning feed | Schedules, webhooks and app events; always on with a Cloud plan |
| Where it runs | Your server, plus CopilotKit Intelligence for conversations | Inside each device, with a free relay or one you host | Your own computer or server; cloud computers with a live desktop on a Cloud plan |
| Data and telemetry | SDK telemetry to PostHog defaults to full capture | No third-party analytics; signed-in chats sync to its relay by default | ~/.openmausbot on your own machine; prompts go only to the model provider you choose |
| Voice | On the roadmap | Input only; calls were removed in 0.1.22 | Live voice calls with your bots on your own OpenAI key |
| Launch reception | A launch tweet seen about 1.17 million times by November 15 | Show HN, 68 points and 21 comments; an arXiv paper | n/a |
What MausBot is, in the same terms
MausBot is not a Muse clone; it is the other shape. Where Muse and every OpenMuse give you one assistant, MausBot is one team of the AI agents you already have: each bot runs on one of 16 agent engines, such as Claude Code, Codex or Grok, or on an API or local model, chosen per bot and switchable mid-conversation, so a Claude Code bot and a Codex bot share a group chat and a Chief of Staff bot hands work to both. Bots run on your own computer, can use your own Chrome, or get a cloud computer with a live desktop you can watch or take over. Every new bot starts at Full access, the engine’s most permissive mode; Ask for approval, Auto-accept edits or Approve for me can be set per bot or thread. Data stays in ~/.openmausbot on your own machine, and prompts go only to the model provider you choose. It installs on macOS, Windows and Ubuntu, has iPhone and Android apps, and is on GitHub under Apache 2.0, apart from an enterprise/ folder. Cloud plans from $15 a month keep bots working with the laptop closed. It runs wherever your own model account or API key works.
What the OpenMuse projects still do better
- OpenFuse has a phone-native UI with rich cards for email, browser previews, PDFs, plans and finance; durable task plans with saved receipts; and a stored review before every send or calendar change.
- nanoMuse drives the apps on an Android phone’s screen as well as the desktop; routes approvals to whichever device is in your hand; stops before deleting, sending or paying; supports twenty-six providers; and has a free model allowance for a first run.
- chyroc’s Open Muse has a signed, notarized Mac app that operates your Mac apps with allow once or allow for this chat, plus blocked apps and folders; it reads Apple Health on demand and offers a Quick Chat overlay over any app.
- OpenFuse and nanoMuse are proactive by design, with ideas, goals and a morning feed; MausBot’s automations run on the schedules, webhooks and app events you set.
The verdict
An open source Muse has to clear three bars: a license that lets you use it, a build you can install, and an agent that can act on your computer under your control. OpenFuse clears the first on paper and fails the second and third, and adds a vendor service the license does not cover. nanoMuse clears the second, half-clears the third by its own account, and is GPL. chyroc’s Open Muse clears all three on a Mac, as a client for Volcano Engine’s managed agents. Digger’s has no license at all. MausBot clears all three as well, and adds the thing none of them has: more than one agent, on more than one engine, in one group chat, with your data on your own machine. MausBot starts bots at Full access, where nanoMuse and chyroc’s ask before they act; set a MausBot bot to Ask if you want the same. For the searcher typing “open muse”, it is the one to install.
Frequently asked questions
- Is there an open source Meta Muse?
- Muse itself is closed, and Meta has not released one. Several projects copy it: CopilotKit’s, now OpenFuse, is MIT but depends on CopilotKit’s Intelligence service in every mode; nanoMuse is GPL-3.0 and self-hostable down to its relay; chyroc’s Open Muse is MIT on Volcano Engine’s managed agents; Digger’s openmuse has no license file at all. MausBot is Apache 2.0, apart from an enterprise/ folder.
- What happened to CopilotKit’s OpenMuse?
- CopilotKit renamed it OpenFuse on November 13, 2026, and the old repository address redirects there. It is the same MIT template, still labeled alpha, still needing a CopilotKit Intelligence key.
- Which OpenMuse is the real one?
- None is official. CopilotKit’s, now OpenFuse, has the most stars, and nanoMuse, which began life as OpenMuse, ships the most installers. Unrelated projects with the name include an archived Hugging Face text-to-image model and a tool that records a Muse EEG headband’s signals.
- Does OpenMuse control my computer like Muse’s Mac app?
- OpenFuse does not: it drives its own browser and an optional Linux workspace on your server, and an open issue asks for it to click and fill forms at all. nanoMuse and chyroc’s Open Muse do, by screenshots, with approvals. MausBot bots run on your own computer, can use your own Chrome, or get a cloud computer with a live desktop you can watch or take over.
- Can I run OpenMuse on my ChatGPT or Claude plan?
- nanoMuse can, by plan sign-in. OpenFuse’s setup uses OpenAI, Anthropic or Google API keys. MausBot runs bots on the Claude, ChatGPT or Grok account, or the API key, you already have, and installs Claude Code or Codex for you.
- Is OpenMuse available outside the US?
- Yes, all of them are code you run, which is one reason people look: Muse itself is available in the US, Canada, Japan and Singapore. nanoMuse’s free relay signs you up with a mainland China phone number or an email address and serves Qwen3.6-27B; your own key or a self-hosted relay is the alternative. MausBot runs wherever your own model account or API key works.
Read next
- OpenMuse vs MausBot, the one-page summary.
- The open source alternative to Meta Muse, MausBot against Muse itself.
- Is Meta Muse open source?
This post is based on the products as they were on . Products change. If something here is out of date, tell us and we will correct it.