openclaw-parallels-smoke

Runs and interprets OpenClaw install, update, and gateway smoke tests on Parallels VMs.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill openclaw-parallels-smoke-amirulandalib
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-parallels-smoke
Source: https://github.com/AmirulAndalib/Vilvona-AI/tree/main/.agents/skills/openclaw-parallels-smoke
Command: npx skills add https://github.com/AmirulAndalib/Vilvona-AI --skill openclaw-parallels-smoke-amirulandalib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Validating OpenClaw installs, upgrades, and gateway behavior across macOS, Windows, and Linux Parallels guest VMs is slow and error-prone, with many transport, snapshot, and updater pitfalls that are hard to diagnose without deep runbook knowledge. ## Core Features & Use Cases - Cross-OS smoke orchestration: Drives fresh-install and same-guest update lanes on macOS, Windows, and Linux guests via pnpm test:parallels:* entrypoints with hard timeouts and per-phase logs. - Update-flow verification: Ensures release-to-dev and npm-tag upgrades exercise the real openclaw update command rather than direct npm installs, with gateway RPC and agent-turn checks afterward. - Failure triage guidance: Encodes known signatures (prlctl transport drops, snapshot hangs, token mismatches, npm debug-log stalls) so failures are diagnosed from the right phase log first. - Use Case: Before publishing a new OpenClaw beta tag, run the aggregate npm-update wrapper with --beta-validation to verify latest-to-beta upgrades and fresh installs across the full OS matrix, then read summary.md for triage. ## Quick Start Run the full Parallels npm update smoke matrix with a 150 minute timeout and JSON summary, then triage any failed lane from its nested phase log.

Frequently Asked Questions about openclaw-parallels-smoke

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run OpenClaw smoke tests on Parallels VMs?

Use the pnpm test:parallels:macos, windows, or linux entrypoints wrapped in a host timeout such as `timeout --foreground 75m`. For full install-plus-update coverage, run the aggregate `pnpm test:parallels:npm-update` wrapper with a 150 minute cap and `--json` for machine-readable summaries.

How do I validate an OpenClaw beta release before publishing?

Run `pnpm test:parallels:npm-update -- --beta-validation beta4 --json`, which resolves the latest matching prerelease, runs latest-to-beta same-guest update coverage, then fresh install smoke for that exact version. Narrow reruns with `--platform macos|windows|linux`.

Why does a Parallels smoke lane hang or time out?

Common causes are prlctl exec transport drops, snapshot-switch hangs, or quiet but healthy npm installs. Inspect the newest /tmp/openclaw-parallels-* run directory and phase log first; on Windows, check the streamed guest npm debug log before assuming a stall.

Does the smoke test verify real OpenClaw update behavior?

Yes. Update lanes must run the guest's installed `openclaw update` command, not a direct npm install of a new package. Verification then checks `openclaw --version`, gateway RPC readiness, and an agent turn after the update completes.

Can I run macOS, Windows, and Linux smoke lanes in parallel?

Yes, independent guest-family lanes can run in parallel when host capacity allows, each in its own shell. Never run two lanes against the same guest family concurrently, and finish any host build or packaging gates before starting the VM matrix.