Self-Check Enhancedv2.1.0

After upgrading OpenClaw, Node.js, or installing new plugins, run the self-check to verify the environment is fully operational. It catches version mismatches, missing agent files, and broken plugin loads before users are affected.

Before investigating a reported issue such as a non-responsive channel or failing skill, run a comprehensive baseline check. The report separates errors, warnings, and passes so engineers can quickly isolate the root cause.

Individual OpenClaw hosts can schedule daily or weekly self-checks to detect disk pressure, expired API tokens, or gateway restarts. The tool never mutates state, so it is safe to run unattended and review reports manually.

When a skill like aliyun-stt fails, the self-check environment scan reveals missing Python modules, absent external binaries, or malformed config.json files. It outputs exact install commands for the user to run manually.

Teams using OpenClaw in regulated environments can use self-check to generate a read-only audit of permissions, required agent files (SOUL.md, USER.md, AGENTS.md), and API key presence without exposing secrets. Reports serve as evidence of configuration integrity.

A hosting company runs self-check across all customer workspaces on a schedule and surfaces reports in a dashboard. Customers receive proactive alerts about disk, token, or gateway issues before downtime occurs.

The self-check skill remains free and open-source to drive adoption, while the maintainers sell expert interpretation of reports and priority fix guidance. This builds trust because the tool never auto-fixes, so users stay in control.

An enterprise plugin bundles self-check with report archiving, trend analysis, and export to compliance tools. Security teams get immutable logs of configuration state and permission checks across fleets of agents.