Openclaw Update

PassAudited by ClawScan on May 1, 2026.

Overview

This is a transparent instruction-only OpenClaw updater, but using it can change the global OpenClaw installation and restart the gateway.

This skill appears coherent for managing OpenClaw updates. Install or use it only if you want the agent to help with OpenClaw version checks and updates, and require confirmation before any global package update, gateway restart, or cron setup.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If run, the agent could change the installed OpenClaw version and briefly disrupt or alter gateway behavior.

Why it was flagged

These commands can update the global OpenClaw installation and restart the gateway. That is aligned with the updater purpose, but it is a high-impact operation that should be user-approved.

Skill content
pnpm add -g openclaw

# Restart gateway after update
openclaw gateway restart
Recommendation

Only allow update and restart commands after confirming the target version, expected downtime, and rollback plan.

What this means

A compromised or unexpected upstream package version could be installed if the update is run without verification.

Why it was flagged

The workflow updates to the latest package rather than a pinned version. This is expected for an updater, but it means the installed code depends on the current upstream package state.

Skill content
# Update to latest version
pnpm add -g openclaw
Recommendation

Review the OpenClaw release notes and package source before updating; consider pinning a specific version for controlled environments.

NoteHigh Confidence
ASI10: Rogue Agents
What this means

A scheduled check could continue running after initial setup and may produce ongoing system activity.

Why it was flagged

The skill suggests optional scheduled checks. This is disclosed and limited to update checking, but cron creates persistent background behavior if the user configures it.

Skill content
**Automatic update checks**: Configure cron jobs for periodic update checks
Recommendation

Configure cron jobs only intentionally, keep them visible and logged, and avoid automatic updates unless separately approved.