parallels-discord-roundtrip

自动执行 Parallels 与 Discord 往返冒烟测试并验证主客机通信链路。

星标

★ 377,401

来源

GitHub

更新于

2026-06-07

// 安全评估低风险

仅提示词，不执行代码
开源可审计
社区验证· 377.4k

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "parallels-discord-roundtrip" 技能：
1. 下载 https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/parallels-discord-roundtrip/SKILL.md
2. 保存为 ~/.claude/skills/parallels-discord-roundtrip/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

验证虚拟机消息回传

输入

请运行 parallels-discord-roundtrip，对 macOS Parallels 环境执行一次冒烟测试：由 guest 通过 Discord 发送消息，host 侧验证接收并回复，再确认 guest 成功读回回复内容，最后输出完整验证结果。

预期产出

返回一次完整的往返测试结果，说明发送、接收、回复与回读是否全部成功，并附带关键验证信息。

回归前检查通信链路

输入

在开始回归测试前，使用 parallels-discord-roundtrip 检查 Parallels 虚拟机与宿主机之间的 Discord 通信链路是否正常，并给出失败步骤定位。

预期产出

输出链路健康检查结果，并明确指出问题出在 guest 发送、host 验证、host 回复还是 guest 回读阶段。

生成自动化验收证明

输入

执行 parallels-discord-roundtrip，并整理成一份可用于验收的测试证明，包含各阶段状态、时间顺序和最终结论。

预期产出

生成适合留档或验收的测试摘要，清楚展示往返通信已被验证或说明失败原因。

// 文档

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 Discord bot token
Discord guild ID
Discord channel ID
OPENAI_API_KEY

Preferred run

export 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

Notes

Snapshot target: closest to macOS 26.3.1 fresh.
Snapshot resolver now prefers matching *-poweroff* clones when the base hint also matches. That lets the harness reuse disk-only recovery snapshots without passing a longer hint.
If Windows/Linux snapshot restore logs show 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.
Harness configures Discord inside the guest; no checked-in token/config.
Use the openclaw wrapper for guest message send/read; node openclaw.mjs message ... does not expose the lazy message subcommands the same way.
Write 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.
Avoid 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.
Full 3-OS sweeps: the shared build lock is safe in parallel, but snapshot restore is still a Parallels bottleneck. Prefer serialized Windows/Linux restore-heavy reruns if the host is already under load.
Harness cleanup deletes the temporary Discord smoke messages at exit.
After a successful Discord roundtrip, shut down the macOS guest before handoff (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.
Per-phase logs: /tmp/openclaw-parallels-smoke.*
Machine summary: pass --json
If roundtrip flakes, inspect fresh.discord-roundtrip.log and discord-last-readback.json in the run dir first.