QoderWake is Alibaba Qoder's product for "autonomous AI employees": a team of digital workers called Wakers that runs as a service on your own machine and takes tasks from DingTalk, Feishu and WeCom groups. muti is a room around the coding agent already running on your machine, where the people you invite send it work and you approve what runs. Both keep the agent local, and both let a group reach it. The differences are about whose agent it is and who says yes.
This comparison uses QoderWake's site, documentation and changelog as of 30 September 2026. For how it sits beside Tencent WorkBuddy and Alibaba's QwenWork, see WorkBuddy, QwenWork and QoderWake.
What is QoderWake?
QoderWake opened a public beta on 26 May 2026 for macOS and Linux, and shipped 1.0 on 3 September. Its first changelog describes it as a way to "build a team of 'digital workers' (Wakers) on your local machine". It installs a local service with a web console on 127.0.0.1 and a CLI. You define Wakers with a name, a duty and a model: Qwen3.8-Max-Preview, DeepSeek-V4, GLM-5.2, Kimi, MiniMax, or an automatic choice. Wakers can form groups with a lead, run multi-step processes through WakerFlow, and ask a human expert when they get stuck.
The group-chat design is thorough. Everyone in a chat mentions the same bot, which routes each task to a Waker. A chat is enabled only after an admin approves it or someone pairs it with a code valid for about ten minutes. Wake-up mode, a switch for each chat, turns a plain connection into full task claiming, routing, records and memory. Work starts from one of four triggers: an IM message, a schedule, a hook event or an API call. Each action can be set to allow, ask or deny. Each role gets its own identity and least-privilege access, and high-risk operations are blocked by default. According to Chinese press, the product ran close to 100,000 digital employees and about two million tasks in its first three months.
What is muti?
muti does not create new agents. It takes the one you already run, such as Claude Code or Codex in a working directory on your computer, with the repository, tools and subscription in place, and gives it a room. A small daemon polls muti over outbound HTTPS, runs each request locally and streams a timeline back: messages, tool-call summaries, approvals and artifacts. Files, environment variables and keys never leave the machine.
People join by invite link and use a browser, or message the agent's own Slack bot. Each person has their own permission: read-only, edit or a standing grant. Four kinds of action stop for the owner whoever asked: pushing to a shared branch, deleting, spending money and touching credentials. Every request has an id and an audit line.
QoderWake: a group mentions one bot, which routes to several Wakers on the local machine. muti: several people in a room reach the owner's own agent, with the owner's approval in between.
Side by side
Where is QoderWake the better answer?
When you want new digital employees rather than access to an existing one. If the job is a standing function, such as triaging support, running a daily report or coordinating a release checklist, then defining Wakers with explicit duties, a lead and a flow is exactly right. Automatic routing means colleagues never have to know which Waker does what. The four triggers let the work start without anyone asking.
It is also the better answer if your company lives in DingTalk, Feishu or WeCom and needs all three. muti's Feishu connector is still in development, and it has no DingTalk or WeCom connector yet.
Where is a room the better answer?
When the capability you want is already configured on someone's laptop. A Claude Code session with the monorepo checked out, the right MCP servers, the database reachable and a year of CLAUDE.md is not something you rebuild as a Waker. It is something you let people reach.
A room is also the better answer when you need the requester and the owner to be different people in the approval model. QoderWake sets allow, ask and deny per action and per role. It does not document what changes when the request comes from a colleague rather than from the machine's owner. In muti, that distinction is the whole design. Each person's permission is their own, and a colleague's request that reaches a push, a delete, a payment or a credential read stops for the owner however trusted the colleague is. See four actions an agent should always ask before doing.
What do the two agree on?
More than either agrees with the cloud personal agents. Both run where the files and logins already are, so no credentials go to a vendor. Both accept the cost: QoderWake's docs say the device must be online when a task needs local files, and muti queues requests in an inbox while the machine sleeps. Both refuse to let a group use the agent just because the bot is in the chat. QoderWake requires pairing, and muti requires an invite. And both keep a record of every task, where a chat window would have kept nothing.
Frequently asked questions
Is QoderWake open source?
We found no source repository for it. QoderWake ships as part of Qoder's paid plans and is included in Qoder Teams; what is public on GitHub is its changelog. muti is a hosted service with a small daemon on your machine, and it is free during the beta.
Can QoderWake run Claude Code?
QoderWake Wakers run on the models Qoder offers, including Qwen, DeepSeek, GLM, Kimi and MiniMax. They are Qoder's own agents, not a bridge to an agent you already use. If the agent you want to share is Claude Code or Codex, muti connects to it directly. See Codex and Claude Code in the same room.
What is a pairing code in QoderWake?
A pairing code is a short-lived message, usually valid for about ten minutes, that QoderWake generates after you choose a Waker. You send it to the target group with an @mention of the bot, or to the bot directly. Once it is paired, that chat may use the Waker. QoderWake's docs warn against posting pairing codes in unrelated groups or keeping them.
Sources
- QoderWake: qoder.com/qoderwake · overview: docs.qoder.com · IM configuration: docs.qoder.com
- QoderWake changelog: github.com/QoderAI/changelog-QoderWake · Qoder pricing: docs.qoder.com
- QbitAI on QoderWake: qbitai.com
Hire new digital employees when the job is new. When the capability already lives on a laptop in your team, give it a room.
Published