Whenever the answer depends on timing, this page attaches a date boundary so the claim does not float free from the source.
Trust questions
The most useful QClaw questions sit right before the install step.
This FAQ keeps the answers practical. It focuses on what is official now, what is still controlled, why the Mac download links are shown, what the Windows status means, how the QQ bot route is publicly described, and when it makes more sense to use the public OpenClaw docs instead of waiting.
That is exactly when the public OpenClaw docs are useful. They give you a transparent fallback instead of forcing you to rely on packaging language alone.
Is QClaw already fully public? +
Not in the broadest sense. The official QClaw page still uses invite-oriented wording, so the safest reading on March 10, 2026 is that public attention is real but access is still controlled.
Why does this site show Mac downloads directly? +
Because those package URLs are actually exposed on the official QClaw page. This site surfaces them directly, but it does not invent a Windows package that is not publicly visible there yet.
What should I do about Windows right now? +
Treat the official page as the source of truth. As of March 10, 2026 it still says coming soon. If you need a transparent path right now, use the public OpenClaw docs instead of random third-party bundles.
Is QClaw the same thing as OpenClaw? +
No. QClaw is the friendlier Tencent-facing packaged story. OpenClaw is the public stack with docs, onboarding, dashboard, gateway checks, and deeper visibility.
How strong is the QQ bot evidence? +
The strongest public description comes from ITHome on March 7, 2026: mobile QQ scan, one-click bot creation, one-minute pairing, three preset commands, and up to five bots per QQ account.
What should my first prompt look like after setup? +
Start with something that returns visible proof: a file list, a screenshot, a short summary, or a task-ready confirmation. Trust usually starts once chat gives something concrete back.