openclaw-parallels-smoke

Runs Parallels VM smoke, upgrade, and rerun tests for OpenClaw across macOS, Windows, and Linux guests.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/srgaba/open-claw --skill openclaw-parallels-smoke-srgaba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-parallels-smoke
Source: https://github.com/srgaba/open-claw/tree/main/project/.agents/skills/openclaw-parallels-smoke
Command: npx skills add https://github.com/srgaba/open-claw --skill openclaw-parallels-smoke-srgaba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying OpenClaw installs, onboarding, gateway health, and upgrades inside Parallels virtual machines is error-prone: each guest OS has different transport quirks, snapshot baselines, and known failure modes that are easy to misread as regressions. This Skill encodes the exact workflows, entrypoints, and interpretation rules so smoke runs are repeatable and results are judged correctly. ## Core Features & Use Cases - Cross-platform smoke workflows: Dedicated flows for macOS, Windows, and Linux guests via pnpm test:parallels:macos, pnpm test:parallels:windows, and pnpm test:parallels:linux, each with correct snapshot selection and prlctl exec transport rules. - Upgrade and rerun verification: npm-install-then-update lanes that install a release baseline, smoke it, install the current main tgz on the same guest, and smoke again with correct gateway restarts and session isolation. - Failure interpretation guidance: Documents known baselines (e.g., precheck=latest-ref-fail, gateway=skipped-no-detached-linux-gateway, rc=255 transport drops) so flakes are not misreported as regressions. - Use Case: After merging a change to OpenClaw's installer, run the Windows same-guest upgrade lane to confirm the gateway restarts cleanly and gateway status passes without token mismatch before shipping. ## Quick Start Ask the agent to run the Parallels smoke suite for a specific guest OS, for example: run the macOS Parallels smoke test against the latest snapshot and interpret the gateway health results.

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 in Parallels VMs?

Use the pnpm entrypoints per platform: pnpm test:parallels:macos, pnpm test:parallels:windows, or pnpm test:parallels:linux. Each flow restores a fresh snapshot, installs OpenClaw, runs onboarding and gateway smoke phases, and writes per-phase logs under /tmp/openclaw-parallels-*.

How do I test an OpenClaw upgrade from latest release to main?

Use pnpm test:parallels:npm-update, which installs the npm release baseline on a fresh snapshot, smokes it, then installs the current main tgz on the same guest and smokes again. Set the default model explicitly and use a fresh --session-id so old session state does not leak into the check.

Why does prlctl exec hang or return rc=255 on Windows guests?

A hung prlctl exec or rc=255 with an empty install log usually indicates a transport drop after guest startup, not an npm or package failure. Prefer the done-file/log-drain PowerShell runner pattern over one long-lived prlctl exec call, and retry after a guest-ready recheck.

Does the Linux Parallels smoke support systemd-managed gateways?

No. The Ubuntu snapshot lacks a usable systemd --user session, and prlctl exec reaps detached child processes, so detached gateway runs are unreliable. Treat gateway=skipped-no-detached-linux-gateway and daemon=systemd-user-unavailable as baseline, not regressions.

Why does openclaw agent report too many arguments in Parallels guests?

Multi-word --message values get split into extra argv tokens when invoked through raw prlctl exec or Start-Process. Wrap the call in a guest shell (/bin/sh -lc on macOS/Linux, & $openclaw inside PowerShell on Windows) so the message passes as a single argument.

When should I not use the Parallels smoke skill?

Do not load it for normal repository work; it is specific to VM-based install, onboarding, and gateway verification under Parallels. For a narrower macOS-only Discord proof run, use the dedicated parallels-discord-roundtrip skill instead.