$ loading_
Run Parallels smoke tests with Discord roundtrip verification across host and guest.
The material describes a workflow that drives a Parallels VM to verify two-way Discord delivery, involving a Discord bot token, SSH-based local config retrieval, VM control, and message roundtrips to Discord. Because it is open-source and heavily adopted, this looks more like an auditable automation workflow than a malicious artifact, with the main concerns being credential handling, network egress, and local/VM operations rather than clear high-risk red flags.
The README explicitly requires a Discord bot token and `OPENAI_API_KEY`, and even shows an example of retrieving the token via `ssh` from `~/.openclaw/openclaw.json`; although it says no token is checked in, the workflow still handles sensitive secrets and carries normal risks of accidental exposure, logging, or misuse across host/guest boundaries.
The material states that it sends and reads messages through Discord to verify two-way delivery, and may also use the OpenAI API; this means test content and nonces are transmitted externally to Discord/related APIs. No unrelated or unknown endpoints are evident, but this contradicts the claim of 'no remote endpoints' and does involve real outbound communication.
The README references `pnpm test`, `ssh`, `prlctl exec/stop`, guest-side scripts, and the `openclaw` wrapper, indicating intended execution of commands on the host, control of Parallels VMs, and actions inside the guest OS. This is a normal high-privilege capability for automation/testing workflows and warrants restricting the runtime environment and target VMs.
The material shows access to host-side `~/.openclaw/openclaw.json`, writing logs under `/tmp/openclaw-parallels-smoke.*`, and configuring Discord plus reading message history inside the guest; there is no sign of broad filesystem scraping, but it does access local configuration, temporary logs, and Discord message data.
The source is an open GitHub repository with extremely high community adoption (about 377k stars), making it far more auditable than a closed-source origin. The license is unspecified and maintenance status is unknown, so specific commits and dependencies should still be reviewed, but no clear supply-chain red flags are evident from the provided material.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "parallels-discord-roundtrip" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/parallels-discord-roundtrip/SKILL.md 2. Save it as ~/.claude/skills/parallels-discord-roundtrip/SKILL.md 3. Reload skills and tell me it's ready
Run parallels-discord-roundtrip for a smoke test in a macOS Parallels environment: send a Discord message from the guest, verify receipt on the host, send a host reply, then confirm the guest reads the reply back successfully, and output the full validation result.
A complete roundtrip test result showing whether send, receive, reply, and readback all succeeded, with key verification details.
Before starting regression testing, use parallels-discord-roundtrip to check whether the Discord communication path between the Parallels VM and host is working correctly, and identify the failed step if any.
A communication health check result that clearly identifies whether the issue occurred at guest send, host verification, host reply, or guest readback.
Execute parallels-discord-roundtrip and compile the results into an acceptance-ready test proof, including stage statuses, event order, and the final conclusion.
An archive-ready or acceptance-ready test summary that clearly shows the roundtrip communication was verified or explains the failure reason.
Use when macOS Parallels smoke must prove Discord two-way delivery end to end.
Cover:
message send to Discordmessage read sees that new messageOPENAI_API_KEYexport OPENCLAW_PARALLELS_DISCORD_TOKEN="$(
ssh peters-mac-studio-1 'jq -r ".channels.discord.token" ~/.openclaw/openclaw.json' | tr -d '\n'
)"
pnpm test:parallels:macos \
--discord-token-env OPENCLAW_PARALLELS_DISCORD_TOKEN \
--discord-guild-id 1456350064065904867 \
--discord-channel-id 1456744319972282449 \
--json
macOS 26.3.1 fresh.*-poweroff* clones when the base hint also matches. That lets the harness reuse disk-only recovery snapshots without passing a longer hint.PET_QUESTION_SNAPSHOT_STATE_INCOMPATIBLE_CPU, drop the suspended state once, create a *-poweroff* replacement snapshot, and rerun. The smoke scripts now auto-start restored power-off snapshots.openclaw wrapper for guest message send/read; node openclaw.mjs message ... does not expose the lazy message subcommands the same way.channels.discord.guilds in one JSON object (--strict-json), not dotted config set channels.discord.guilds.<snowflake>... paths; numeric snowflakes get treated like array indexes.prlctl enter / expect for long Discord setup scripts; it line-wraps/corrupts long commands. Use prlctl exec --current-user /bin/sh -lc ... for the Discord config phase.prlctl stop "macOS Tahoe"). The macOS smoke harness should do this automatically after successful Discord proof; still stop the VM manually after ad-hoc Discord checks. Do not leave the Discord-configured VM running; it can keep reading/posting in #maintainer and spam Discord after the proof is complete./tmp/openclaw-parallels-smoke.*--jsonfresh.discord-roundtrip.log and discord-last-readback.json in the run dir first.discord=pass for that laneopenclaw message read outputFetch GitHub issues, create fixes, open PRs, and handle reviews.
Convert text to speech locally and offline with sherpa-onnx, no cloud needed.
Regenerate OpenClaw release changelog sections from Git history before releases.
Prepare and verify OpenClaw stable or beta releases and release notes.
Automate web page workflows, login checks, tab handling, and recovery steps.
Verify an OpenClaw release is fully published and working across all channels.
Run, debug, rerun, and interpret OpenClaw Parallels install and smoke checks.
Manage Parallels virtual machines and run commands inside them.
Chat directly with the Discord-backed OpenClaw agent in real time.
Interact with Discord using natural language for messaging, server management, and user actions.
Speed up complex tasks with parallel execution while preserving correctness.
Run isolated browser instances in parallel for independent web operations and testing.