Menu
Use when a developer needs to install, verify, or repair the Wendy CLI before using `wendy run`, `wendy discover`, or device workflows.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when creating, validating, or repairing a Wendy project scaffold, adapting Wendy templates, `wendy.json`, JSON schema setup, or project entitlements with `wendy init`, `wendy json`, or `wendy project entitlements`.
Use when creating a Wendy app from an existing Wendy template or sample, especially when the user names an app archetype such as realsense-camera, camera-feed, camera-feed-yolo, voice-assistant, audio, fullstack, simple-api, or asks to create a Wendy app in a new directory.
Use when a developer or coding agent needs Wendy CLI-native device operations: discover devices, set defaults, inspect device version/system/hardware/WiFi state, update the agent, or gather evidence before SSH/debugging.
Use when configuring, verifying, or explaining the Wendy CLI MCP server for AI assistants with `wendy mcp setup` or `wendy mcp serve`, especially Claude Code, Claude Desktop, Codex, or device-tool access.
Use when debugging WendyOS, Jetson, Raspberry Pi, USB-C host mode, containerd, GPU/audio/video entitlements, or a `wendy run` issue that only appears on a live device.
Use when a developer wants to build, deploy, run, detach, stream logs, start, stop, list, remove, or clean up Wendy apps with `wendy build`, `wendy run`, `wendy device apps`, `wendy device logs`, telemetry streams, or volumes.
| name | wendy-install |
| description | Use when a developer needs to install, verify, or repair the Wendy CLI before using `wendy run`, `wendy discover`, or device workflows. |
Use this when the user asks to set up Wendy, install the Wendy CLI, verify their local Wendy installation, or prepare a machine for Wendy development.
Installing this plugin must not silently install Wendy CLI. Treat Wendy CLI installation as an explicit task that the agent performs after the user asks for setup or after the user approves a proposed setup step.
Do not run an OS-level installer if wendy --version already works unless the user explicitly asks to reinstall or upgrade.
For the full plugin workflow, including wendy mcp and wendy device hardware, require Wendy CLI 2026.04.30-211221 or newer. If the installed version is older, tell the user which workflow is blocked and recommend updating the CLI before using MCP or hardware inspection.
Use the current OS, not assumptions:
uname -s
command -v wendy || true
wendy --version
On Windows, use PowerShell equivalents:
Get-Command wendy -ErrorAction SilentlyContinue
wendy --version
macOS and Linux:
curl -fsSL https://install.wendy.sh/cli.sh | bash
Windows:
winget install WendyLabs.Wendy --source winget
If a shell needs reloading after installation, tell the user exactly which command to run or open a new terminal. Do not assume PATH changes have already propagated.
After install or repair:
wendy --version
wendy discover --json
If the user is working from source inside /Users/maximilianalexander/wendylabsinc/wendy-agent, use wendy-dev for source CLI testing when that shell function is available.
If wendy discover --json finds no device, do not treat that as a failed CLI install. Separate CLI installation from device reachability, then move to wendy-device-debug if the task is about a missing or unreachable device.