Key takeaways
- 17.4K stars and 2.6K forks in under four months — launched February 24, 2026 as CoPaw, rebranded to QwenPaw on April 12, 2026 for deeper Qwen ecosystem integration
- Memory-evolving architecture built on AgentScope + ReMe — the agent stores long-term experience and user preferences, getting smarter with use
- Widest deployment menu in the category: pip, install script, Docker, Windows/macOS desktop app (beta), and ModelScope Studio cloud — all Apache 2.0, free
FAQ
What is QwenPaw?
A self-hosted personal AI assistant from Alibaba's AgentScope team (QwenPaw = Qwen Personal Agent Workstation) that connects to DingTalk, Feishu, WeChat, Telegram, Discord and more, with evolving memory and a plugin market.
How much does QwenPaw cost?
Free and open source under Apache 2.0. You pay only for LLM API usage, or nothing if you run local models via Ollama, llama.cpp, or the CoPaw-Flash fine-tunes.
Does QwenPaw require Qwen models?
No. Qwen is the default emphasis, but it supports OpenAI, Gemini, and local backends (llama.cpp, Ollama, LM Studio), plus fine-tuned CoPaw-Flash models (2B/4B/9B) for fully local operation.
How is QwenPaw different from AstrBot?
Both are China-built multi-channel assistants, but QwenPaw is a personal assistant with evolving memory backed by Alibaba's AgentScope framework, while AstrBot is chatbot infrastructure with a larger plugin ecosystem.
Executive Summary
QwenPaw is a self-hosted personal AI assistant from Alibaba's AgentScope team — the name stands for Qwen Personal Agent Workstation. It launched on February 24, 2026 as CoPaw and rebranded to QwenPaw on April 12, 2026, signaling "deeper Qwen ecosystem integration, same open-source mission."[1] The pitch: an assistant that is "easy to install, deploy locally or in the cloud, connect across channels, extend with ease" — reachable from DingTalk, Feishu, WeChat, Telegram, Discord, QQ, and iMessage.[2]
Growth has been fast: 17.4K GitHub stars and 2.6K forks as of June 2026, less than four months after first release.[1] Its differentiator is the memory-evolving architecture built on AgentScope, AgentScope Runtime, and the ReMe memory module — the agent "learns from interactions, reflects on experience, and proactively serves you."[3] Release cadence is aggressive, with v1.1.11 shipping June 10, 2026 and two patch releases the following day.[4]
| Attribute | Value |
|---|---|
| Company/Creator | Alibaba AgentScope team (agentscope-ai) |
| Founded | February 2026 (as CoPaw); rebranded April 12, 2026 |
| GitHub Stars | 17.4K ★ (as of June 2026) |
| License | Apache 2.0 |
| Language | Python backend, TypeScript frontend |
Product Overview
QwenPaw runs as a self-hosted assistant you reach through your existing chat apps. Install via pip, Docker, or the desktop app; configure models in the web console (Settings → Models); connect channels; and the agent handles scheduling, document processing, and recurring digests while accumulating memory of your preferences.[2]
Key Capabilities
| Capability | Description |
|---|---|
| Multi-channel | DingTalk, Feishu, WeChat, Telegram, Discord, QQ, iMessage, Tencent Yuanbao[1] |
| Evolving memory | ReMe module stores long-term experience and user preferences, locally or in cloud[3] |
| Plugin Market | AgentScope Platform integration; custom skills auto-loaded, "no lock-in"[2] |
| Skills system | Decoupled extension system based on the anthropics/skills specification[3] |
| Built-in tools | Scheduling, PDF/Office processing, news digest[2] |
| Local models | CoPaw-Flash fine-tunes (2B/4B/9B) for personal-assistant scenarios[5] |
| Multi-agent | Multiple assistants run independently and collaborate via AgentScope[3] |
Product Surfaces
| Surface | Description | Availability |
|---|---|---|
| Web console | Configuration, chat, model settings | GA |
| Chat channels | DingTalk, Feishu, WeChat, Telegram, Discord, QQ, iMessage | GA |
| Desktop app | Windows and macOS (Tauri-based) | Beta |
| Cloud | ModelScope Studio one-click deploy | GA |
Technical Architecture
QwenPaw is a Python backend (the bulk of the codebase) with a TypeScript/Node.js web frontend, sitting on Alibaba's agent stack: AgentScope for agent logic, AgentScope Runtime for execution, and ReMe for memory management.[3]
pip install qwenpaw
# or
docker pull agentscope/qwenpaw
Key Technical Details
| Aspect | Detail |
|---|---|
| Deployment | pip, install script (macOS/Linux/Windows), Docker (Docker Hub + Alibaba Cloud registry), desktop app (beta), ModelScope Studio[2] |
| Model(s) | Qwen-first defaults; OpenAI, Gemini; local via llama.cpp, Ollama, LM Studio; CoPaw-Flash 2B/4B/9B fine-tunes[5] |
| Integrations | 8 chat channels, Plugin Market, anthropics/skills-spec extensions[1] |
| Open Source | Apache 2.0, github.com/agentscope-ai/QwenPaw[1] |
Strengths
- Corporate backing with open license — Built by Alibaba's AgentScope team but Apache 2.0 licensed, with weights for its fine-tuned models published openly[5]
- Genuinely local option — The HN submission billed it as "a truly local OpenClaw alternative with customized models (2B, 4B, 9B)" — small fine-tunes mean it can run without any API key[6]
- Memory architecture — ReMe-backed long-term experience storage is a structural differentiator versus stateless chatbot frameworks[3]
- China + Western channel coverage — DingTalk, Feishu, WeChat, and QQ alongside Telegram, Discord, and iMessage[1]
- Rapid iteration — v1.1.11 on June 10, 2026, with two follow-up patches within 24 hours[4]
- Deployment flexibility — pip, script, Docker, desktop beta, and cloud studio cover hobbyist through production[2]
Cautions
- Issue backlog — 871 open issues as of June 2026, large relative to project age[1]
- Qwen-first orientation — Multi-provider support exists, but the rebrand explicitly deepens the Qwen tie; roadmap priorities will likely favor Alibaba's model family[1]
- Naming churn — A rebrand seven weeks after launch (CoPaw → QwenPaw) fragments search results, docs links, and package references[1]
- Thin independent validation — Almost no English-language community discussion exists yet (see below); adoption signals rest mostly on GitHub metrics
- Desktop app is beta — Windows/macOS app shipped but is explicitly labeled beta[4]
What Developers Say
Substantive independent community discussion is scarce as of June 11, 2026. The only Hacker News submission (March 31, 2026, as CoPaw) drew 2 points and a single comment — from the submitter:[6]
"CoPaw comes with CoPaw-Flash models fine-tuned for personal assistant scenarios" — ekzhu, the HN submitter
Searches of Reddit (including r/LocalLLaMA) surfaced no QwenPaw or CoPaw threads, and no substantive English-language reviews were findable on Chinese developer aggregators. Third-party coverage is limited to trade press like MarkTechPost's launch writeup.[3] The absence of organic developer discussion — for a 17.4K-star project — is itself a data point: star growth appears driven by the AgentScope/Qwen ecosystem and Chinese-language channels rather than Western community word-of-mouth.
Pricing & Licensing
| Tier | Price | Includes |
|---|---|---|
| Open source | Free | Full product: all channels, memory, plugin market, desktop app |
Licensing model: Apache 2.0 — permissive, commercial use allowed.[1]
Hidden costs: LLM API usage (avoidable with local CoPaw-Flash/Ollama models), hosting for always-on deployment, and per-channel bot credentials/approvals (WeChat and DingTalk setup is nontrivial).
Competitive Positioning
Direct Competitors
| Competitor | Differentiation |
|---|---|
| OpenClaw | Western-focused, far larger codebase; QwenPaw pitches itself as the truly-local alternative with small fine-tuned models[6] |
| AstrBot | Similar China+Western channel coverage with a larger plugin ecosystem (800+); QwenPaw counters with evolving memory and Alibaba's agent stack |
| NanoBot | Lighter (pip-install single process, 44K stars, 14+ channels); QwenPaw is heavier but adds desktop app, plugin market, and ReMe memory |
When to Choose QwenPaw Over Alternatives
- You want a personal assistant that accumulates long-term memory, not just a chatbot router
- You need DingTalk/Feishu/WeChat plus Telegram/Discord from one deployment
- You want fully local operation with purpose-built small models (CoPaw-Flash 2B-9B)
- You are already in the Qwen/AgentScope/ModelScope ecosystem
Ideal Customer Profile
Best fit:
- Developers in the Qwen/Alibaba Cloud ecosystem wanting a self-hosted assistant
- Users who need Chinese IM channels (DingTalk, Feishu, WeChat) with Western ones
- Privacy-conscious users who want local-only models with no API dependency
- Tinkerers who want a desktop app rather than server-only deployment
Poor fit:
- Teams wanting a mature, community-vetted project with deep English-language support
- Users who want the largest plugin ecosystem (AstrBot) or the lightest install (NanoBot)
- Anyone uncomfortable betting on a project that renamed itself within two months of launch
Viability Assessment
| Factor | Assessment |
|---|---|
| Financial Health | Backed by Alibaba's AgentScope team; no separate funding needed |
| Market Position | 17.4K stars in under 4 months; strong in China, unproven in the West |
| Innovation Pace | Very high — multiple releases per week as of June 2026[4] |
| Community/Ecosystem | 2.6K forks but thin independent discussion; plugin market still young |
| Long-term Outlook | Tied to Alibaba's Qwen strategy — durable backing, but priorities follow the sponsor |
QwenPaw's trajectory looks like a corporate-sponsored land grab executed well: fast releases, broad deployment options, and open weights. The open question is whether it builds an organic community beyond the Qwen ecosystem or remains primarily an Alibaba showcase.
Bottom Line
QwenPaw is the most credible China-built entrant in the personal-agents category since AstrBot — same channel breadth, but with a real memory architecture and small local models that no competitor ships. The Apache 2.0 license and 17.4K-star growth in four months make it impossible to ignore. What it lacks is independent validation: almost nobody outside the AgentScope orbit is publicly writing about using it, and an 871-issue backlog plus a launch-quarter rebrand suggest a project still finding its footing.
Recommended for: Qwen-ecosystem developers, users needing Chinese + Western IM channels, and privacy-first users who want fully local models.
Not recommended for: Teams that need community-proven stability or primarily English documentation and support.
Outlook: Durable as long as Alibaba funds it; watch whether the plugin market and Western community traction materialize through 2026.
Research by Ry Walker Research • methodology