Normal setup and repair paths are documented across install, CLI, and gateway docs. Platform-specific Windows paths are tracked in the Windows via WSL2 and Native Windows rows.

Core architecture, auth, pairing, protocol docs, daemon docs, and CLI runbooks are broad and current.

Main loop, models, provider routing, and tool streaming are first-class, but provider behavior shifts weekly and needs scenario proof per release.

Strong docs and active implementation. Maturity depends on transcript durability, compaction quality, and cross-client parity.

Many channels share Gateway delivery and routing contracts, but channel behavior varies by upstream API and account-policy constraints.

OTel, Prometheus, logging, and diagnostics docs exist. Needs a public "what operators should look at first" maturity pass.

Web UI is documented with pairing, chat, PWA, Talk, push, and remote Gateway flows. Promote after cross-browser and mobile-PWA scorecards.

Broad docs and strong internal runtime evidence exist across manifests, discovery, loading, provider/tool architecture, and approval boundaries. Keep the row at beta until public SDK API/subpaths and external distribution proof are stronger.

Good docs and hardening surfaces exist. Promote after regular upgrade/security scenario runs prove no setup regressions.

Documented and usable, but scenario proof should cover unattended delivery, retries, and failure visibility.

Broad capability surface exists, but provider variance, file limits, and node/app parity make this not stable yet.

Multiple implementations exist across Control UI, apps, and providers. Needs latency, failure-mode, and setup scorecards before beta.

Present in docs and source, but less visible as a primary user workflow. Needs explicit scenario definition.

Public docs and ecosystem concept exist. Needs install, trust, update, rollback, and compatibility scorecards.

OpenClaw App SDK is a distinct external app contract separate from Gateway runtime and Plugin SDK. Current scoring shows a real @openclaw/sdk path with gaps around public packaging, auto-discovery, approvals, helpers, and compatibility.

Node runtime is recommended, systemd user service is documented, and VPS/container guidance is broad.

LaunchAgent service path, local/remote Gateway modes, CLI install, and app integration are documented.

Official Google Play distribution exists, source build/run docs are maintained, and the Android app is documented as a normal companion node for users.

Official App Store distribution exists, relay-backed push is documented, and the iOS app is documented as a normal companion node for users.

Install docs exist and are common deployment paths. Promote after recurring release smoke captures upgrade and volume behavior.

Recommended Windows path with systemd/user-service guidance and boot-chain docs. Promote after repeated install/update scorecards.

Platform docs exist and Gateway path is Linux-based. Needs hardware-specific release smoke proof to move higher.

Rich menu bar app, permissions, node mode, Canvas, voice wake, WebChat, and remote mode exist. Still fast-moving enough to avoid Stable.

Core CLI/Gateway flows work, but docs still recommend WSL2 for the full experience and list native caveats.

Kubernetes hosting is a distinct Kustomize-based cluster deployment path. Current scoring shows a real minimal deployment path with gaps around Kubernetes-specific CI, ingress/TLS/NetworkPolicy packaging, backup/restore, and production exposure hardening.

Optional install flow. Needs clearer support promise before alpha/beta promotion.

Source has Watch app/extension surfaces; public docs do not yet present this as a user feature.

Docs say native Linux companion apps are planned; Gateway is the supported Linux path today.

Planned only.

Deep docs and broad feature coverage. Voice/delegation paths should stay separately scored as beta/alpha.

Core channel is mature enough for regular use, but high-variance UX and media edge cases need recurring scenario proof.

First-class channel docs and routing surface. Needs workspace install/admin scenario scorecards.

Supported iMessage runs through imsg on a signed-in macOS Messages host; legacy BlueBubbles configs require migration. Keep macOS permissions, SSH wrapper, SIP/private API, and migration caveats visible.

Core path is important and documented; upstream Baileys/session volatility keeps it below Stable.

Supported via bundled plugin. Needs bridge, auth, and room lifecycle scorecards.

Documented channel, but enterprise/admin setup raises maturity risk.

Enterprise auth/admin flows need explicit scenario proof.

Supported channel docs exist; needs stronger install and reconnect proof.

Important regional coverage, but public support level should be calibrated per account type, upstream approval, and maintainer proof.