AI Coding Agent Setup
Install the Wendy plugin for Codex or Claude Code, then start a Wendy project with an AI coding agent
This guide assumes you want Codex or Claude Code to do the coding work for you. You install the Wendy plugin, ask the agent to install or verify the Wendy CLI, then ask it to create and run a Wendy app.
Install the Wendy plugin
Choose the coding agent you will use.
Add the Wendy plugin marketplace:
codex plugin marketplace add wendylabsinc/wendy-agentic-codingOpen Codex and install the plugin from the plugin browser:
codex
/pluginsStart a new Codex thread and mention the plugin as @Wendy:
Use @Wendy to install Wendy CLI, verify my Wendy CLI version, discover my Wendy device, and create a Wendy app for this project.Add the Wendy plugin marketplace and install the plugin:
claude plugin marketplace add wendylabsinc/wendy-agentic-coding
claude plugin install wendy-agentic-coding@wendy-agentic-codingRestart Claude Code or reload plugins:
/reload-pluginsStart with the Wendy install command:
/wendy-agentic-coding:wendy-installLet the agent install Wendy CLI
The plugin does not silently install system tools. Ask Codex or Claude Code to install or verify Wendy CLI, and let it show you the command before it runs it.
The agent should use these commands:
curl -fsSL https://install.wendy.sh/cli.sh | bashVerify the installation:
wendy --version
wendy discover --jsoncurl -fsSL https://install.wendy.sh/cli.sh | bashVerify the installation:
wendy --version
wendy discover --jsonwinget install WendyLabs.Wendy --source wingetVerify the installation:
wendy --version
wendy discover --jsonFor the full agent workflow, including Wendy MCP and hardware inspection, use Wendy CLI 2026.04.30-211221 or newer. If your package manager installs an older version, ask the agent to update Wendy from the latest release at github.com/wendylabsinc/wendy-agent/releases.
Start a project from a template
For a new app, ask the agent to search Wendy templates before it writes code from scratch. The Wendy plugin teaches Codex and Claude Code to prefer the local templates repo or github.com/wendylabsinc/templates when it is unsure.
Example prompt:
Use @Wendy to create a Wendy app in ./foo-bar from the realsense-camera template.
Search local templates first; if source behavior is unclear, check wendylabsinc/templates before writing code.
Validate wendy.json, discover my device, and tell me the exact command to run the app detached.The agent should inspect the matching template's template.json, wendy.json, Dockerfile, and source files, then create or adapt the app in your requested directory.
Common agent prompts
Use these prompts as starting points.
Use @Wendy to create a Wendy Python app in ./robot-camera from the closest camera template. Validate wendy.json and explain the entitlements.Use @Wendy to run this app on my Wendy device in detached mode, then stream the logs and summarize any startup errors.Use @Wendy to inspect my device hardware and update wendy.json so the app has only the entitlements it needs./wendy-agentic-coding:wendy-template create a Wendy Python app in ./robot-camera from the closest camera template/wendy-agentic-coding:wendy-run run this app detached, then stream logs and summarize startup errors/wendy-agentic-coding:wendy-device-ops inspect my device hardware and recommend the smallest wendy.json entitlement setWhat the agent should do
For a new Wendy app, expect Codex or Claude Code to:
- Check
wendy --versionandwendy discover --json. - Search local templates or
wendylabsinc/templatesfor the closest app archetype. - Create or adapt the app in your requested directory.
- Choose the smallest practical
wendy.jsonentitlements. - Run
wendy json validate. - Use
wendy run --yes --detach --device <hostname>for long-running apps. - Stream logs with Wendy device log commands and summarize actionable failures.