Parallels Discord Roundtrip

This is an end-to-end integration test that spins up a fresh macOS Parallels VM, installs OpenClaw, and proves Discord bidirectional messaging works by having the guest send a message with a nonce, the host verify it appears in the channel, the host post a reply, and the guest read it back. It's smoke testing for the full Discord integration stack, not a development tool. The setup is fiddly: you need to avoid prlctl enter for config because it corrupts long commands, write guild config as strict JSON instead of dotted paths because snowflakes get parsed as array indexes, and remember to shut down the VM afterward or it keeps spamming your Discord channel. If you're maintaining OpenClaw's Discord bridge or need to verify Parallels snapshot restore didn't break message delivery, this is the harness.

skills.sh installs: 196
GitHub stars: 376.2K
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add steipete/clawdis --skill parallels-discord-roundtrip --agent claude-code

Installs into .claude/skills of the current project.

Files

Parallels Discord Roundtrip

Use when macOS Parallels smoke must prove Discord two-way delivery end to end.

Goal

Cover:

install on fresh macOS snapshot
onboard + gateway health
guest message send to Discord
host sees that message on Discord
host posts a new Discord message
guest message read sees that new message

Inputs

host env var with the token for a dedicated, operator-approved QA bot
operator-approved QA guild and channel IDs
OPENAI_API_KEY

Preferred run

Load OPENCLAW_PARALLELS_DISCORD_TOKEN through the approved secret source. Set OPENCLAW_PARALLELS_DISCORD_GUILD_ID and OPENCLAW_PARALLELS_DISCORD_CHANNEL_ID to the approved QA destination. The harness configures that bot inside the selected guest.

pnpm test:parallels:macos \
  --discord-token-env OPENCLAW_PARALLELS_DISCORD_TOKEN \
  --discord-guild-id "$OPENCLAW_PARALLELS_DISCORD_GUILD_ID" \
  --discord-channel-id "$OPENCLAW_PARALLELS_DISCORD_CHANNEL_ID" \
  --json