Treat each item based on its source type: official page, public reporting, or public docs. That prevents a lot of accidental overclaiming.
Dated timeline
The useful QClaw updates are the ones tied to exact dates and named sources.
The timeline stays narrow on purpose. The priority is simple: what the official page says now, what the March 7 and March 9 public reports add, and where the public OpenClaw docs remain the clearer reference underneath.
The QClaw story is moving fast. Exact dates are the difference between a trustworthy guide and a stale rumor page.
The official page still exposes two Mac packages and a Windows coming-soon state
This is the most practical current update because it answers the first download question: is anything official live yet, and for which platform?
View official pageThe official page still anchors the product around auto deploy, open and use, WeChat direct conversation, and 5000+ skills
That keeps the public story centered on a chat-first packaged experience instead of a technical runtime alone.
View official pageThe OpenClaw relationship becomes easier to describe publicly
TechNode’s reporting frames QClaw as one-click packaging around OpenClaw. That makes the stack easier to read.
Read reportThe QQ bot path becomes concrete enough to verify yourself
Public details include mobile QQ scan, one-click bot creation, one-minute pairing, three preset commands, and up to five bots per QQ account.
Read reportThe fallback onboarding path remains transparent
Node 22+, onboard install, dashboard, and gateway status remain clearly described in the public docs.
Open docsRelated queries keep clustering around Tencent, OpenClaw, WeChat, QQ, and Little Lobster naming
That matters because it shows the search intent is not random. The Tencent story, the public stack, and the chat channels keep appearing together.
View signal summary