Automates OpenClaw upgrades on macOS with verification and smoke tests.
npx skills add https://github.com/cncoder/oneclaw --skill openclaw-upgrade-cncoder
Please help me install this Agent Skill. Skill: openclaw-upgrade Source: https://github.com/cncoder/oneclaw/tree/main/skills/openclaw-upgrade Command: npx skills add https://github.com/cncoder/oneclaw --skill openclaw-upgrade-cncoder
Upgrading OpenClaw to a new version on macOS can be risky without a structured, end-to-end process. This skill provides a repeatable runbook to perform the upgrade safely, validate prerequisites, migrate configurations, re-register launch agents, and verify the deployment.
Tell OpenClaw to upgrade to the latest stable version and verify the deployment end-to-end.
High-intent search queries and answers about installing and using this skill.
To upgrade OpenClaw on macOS safely, use an automated end-to-end workflow that performs version checks, installation, configuration migration, and launchd service re-registration. This structured runbook ensures a repeatable upgrade process without risking your deployment.
The OpenClaw version migration process covers Phase 0 through Phase 7 workflows. It includes verifying prerequisites, installing the target version, migrating configurations, re-registering launch agents, and running smoke tests across gateway and daemon components.
Yes, you need pnpm and Node.js to run an OpenClaw upgrade. The upgrade workflow also requires proper AWS Bedrock and OpenClaw prerequisites, plus specific environment configuration for proxies and launch agent plist files.
You verify OpenClaw gateway and daemon status after an upgrade by running built-in end-to-end smoke tests. These tests check overall OpenClaw health and confirm that both gateway and daemon components are functioning correctly post-migration.
The best way to handle a failed OpenClaw upgrade on macOS is to follow the provided rollback guidance. This structured approach helps you restore a known-good version if anything goes wrong during the installation or migration process.
Your OpenClaw launchd service might not start after upgrading if the launch agent plist was not properly re-registered during the migration phase. The upgrade workflow explicitly handles re-registration of launchd services to prevent this issue.
joaopiccioni44Install and configure OpenClaw on macOS, Linux, and Docker.
cyberpunk042Identify failing deployments and roll back to the last known good state.
veawhoDiagnose and fix macOS Gatekeeper and launchd failures for Go binaries.
jm199seoUpgrade gstack installations across global, local, and vendored environments.
