QwenPaw v1.1.3: Alibaba's OpenClaw Competitor Ships ACP Server, Proactive Messaging & Shell Guard
QwenPaw — formerly CoPaw, now rebranded to reflect deep integration with Alibaba's Qwen open-source ecosystem — shipped v1.1.3 today. It's one of the most capable OpenClaw-adjacent personal AI agent projects, and it's moving fast.
What QwenPaw Is
QwenPaw is a self-hosted personal AI assistant with a pitch nearly identical to OpenClaw:
- Deploy locally or in the cloud — data stays on your machine
- Skills-based extension system — custom skills auto-loaded, no lock-in
- Multi-agent collaboration — agents with independent roles, inter-agent communication
- Multi-layer security — tool guard, file access control, skill security scanning
- Multi-channel — DingTalk, Feishu, WeChat, Discord, Telegram, and more
The key difference: QwenPaw defaults to Qwen models and is purpose-built for the Chinese tech stack (DingTalk, Feishu, WeChat) while also supporting Western channels. The April 12 rebrand from CoPaw to QwenPaw signals a tighter alignment with Alibaba's model ecosystem going forward.
What's New in v1.1.3 (April 22)
QwenPaw as ACP Server
This is the headliner. QwenPaw can now act as an ACP (Agent Communication Protocol) server — meaning other agents and tools can connect to it as a runtime, not just use it as a standalone assistant. This is the architecture OpenClaw's multi-agent sub-agent system uses. QwenPaw supporting it means cross-platform agent orchestration becomes possible.
Proactive Agent Messaging
Agents can now initiate messages proactively — without waiting for user input. This is equivalent to OpenClaw's heartbeat system: scheduled or triggered outbound messages from the agent to the user. Previously QwenPaw was reactive-only.
Shell Evasion Guard
A new security layer that detects and blocks shell evasion attempts — prompt injection patterns that try to get the agent to execute unintended shell commands. With SecurityScorecard's report this week showing 63% of exposed agent deployments vulnerable to RCE, this is a timely addition.
Console Plugin System
Plugins can now expose interfaces directly in the QwenPaw console — similar to OpenClaw's canvas system. Enables richer interactive UIs without leaving the agent interface.
Backup & Restore
Full system backup and restore for agent state, memory, and configuration. OpenClaw doesn't have a native backup system — this is a genuine gap QwenPaw is filling.
Agent Statistics Page
Usage metrics, token consumption, and task history per agent. Useful for monitoring cost and activity across multi-agent setups.
QwenPaw vs. OpenClaw: Where They Stand
| Feature | OpenClaw | QwenPaw v1.1.3 |
|---|---|---|
| Default model | Any (Kimi K2.6 as new default) | Qwen ecosystem |
| Channels | 20+ (WhatsApp, Telegram, Discord, Signal, iMessage…) | DingTalk, Feishu, WeChat, Discord, Telegram |
| Skills/extensions | 13,700+ community skills, ClawHub | Built-in + custom, smaller catalog |
| ACP support | Yes (as client + server) | Yes as of v1.1.3 (server) |
| Proactive messaging (heartbeat) | Yes, mature | Yes as of v1.1.3 |
| Backup/restore | No native system | Yes as of v1.1.3 |
| Shell security guard | Sandbox + elevated permissions model | Shell Evasion Guard as of v1.1.3 |
| Western market fit | Strong (US/EU channels, English-first) | Growing (Chinese market primary) |
| Community/ecosystem | 247K GitHub stars, massive | Smaller but backed by Alibaba |
Why This Matters
QwenPaw shipping proactive messaging and ACP server support in the same release brings it architecturally close to OpenClaw's core feature set. The backup/restore system is a genuine advantage OpenClaw doesn't match yet. And Shell Evasion Guard is a smart security response to the current threat landscape.
Alibaba's backing gives QwenPaw distribution advantages in China that no Western alternative can match. For the global market, OpenClaw still has the larger ecosystem and deeper Western channel support — but QwenPaw is closing the gap faster than most OpenClaw alternatives have.
For users evaluating which platform to commit to: OpenClaw remains the better choice for Western channels, larger skill catalogs, and established community support. QwenPaw is worth watching if your workflow is China-adjacent or you want native Qwen model integration.
Either way — both platforms reward a well-configured setup. A ClawReady setup on OpenClaw gives you everything QwenPaw is catching up to, configured correctly from day one.