菜单
Manage and open the opencode-pilot remote control dashboard for Codex sessions. Use when the user wants to monitor sessions remotely, get permission notifications on their phone, or open a web dashboard for codex.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/lesquel/open-remote-control --skill remote命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | remote |
| description | Manage and open the opencode-pilot remote control dashboard for Codex sessions. Use when the user wants to monitor sessions remotely, get permission notifications on their phone, or open a web dashboard for codex. |
The user has opencode-pilot installed (an HTTP server on localhost:4097 that exposes a web dashboard, SSE event stream, and permission queue). This skill lets you help them connect codex to it.
First, check status: call pilot.status MCP tool. If running: false, instruct the user to start it (the tool's error message includes the exact command for their OS).
If hooks not configured yet: call pilot.configure_hooks (defaults to project-local .codex/config.toml). This returns a dry-run preview first — show it to the user, ask them to confirm. If they confirm, call again with { confirm: true }.
To open the dashboard: call pilot.open_dashboard. Returns the URL the user should open in their browser. If they're on phone, the response includes a QR code (ASCII).
/remoteRun pilot.status then pilot.open_dashboard and present the dashboard URL with a one-line summary of what they can do there.
DO NOT try to start it yourself — codex plugins cannot launch background processes. Tell the user the exact command from the error response and wait for them to start it.