Wendy

Open-source OS, CLI and cloud for coding agents building robots

Advanced API
Screenshot of Wendy, Open-source OS, CLI and cloud for coding agents building robots

What is Wendy?

Wendy is an open-source OS, CLI and cloud that lets coding agents simulate, ship and operate robots and drones, moving one project from a laptop simulation to Jetson, Raspberry Pi and other real hardware.

Wendy is a full-stack platform for physical AI that covers the path from a simulated robot on a laptop to a fleet of real machines. It combines an open-source operating system (WendyOS), a command line tool, a device agent and a cloud service, all designed so that a coding agent such as Claude Code or Codex can drive each stage. The same project moves from simulation to hardware without being rewritten. The workflow has three stages. In simulation, a robot runs inside a WendyOS virtual machine on the developer's computer, with MuJoCo physics, a locomotion policy and ROS 2 beside the app. Profiles exist for the Unitree Go2 and G1 (both marked preview), and there is a twelve-drone formation example. When the simulation behaves, the same `wendy run` command targets a real device: the CLI builds the app into a container, finds the board over USB-C or the local network, and sends only the missing chunks. Logs stream back so the agent can see what the device sees. Once deployed, the Wendy Agent provides telemetry through an OpenTelemetry endpoint, pinned deploys without SSH, over-the-air updates and, in beta, fleet tools through Wendy Cloud. Agent integration is central. Claude Code and Codex use a plugin, while Cursor, Windsurf and Claude Desktop connect through an MCP server exposing 44 tools, each tagged read-only, mutating or destructive. Most CLI commands answer in JSON when no terminal is attached, and a `wendy.json` manifest declares the hardware an app may use. Provisioned devices accept API calls only over mutual TLS. Supported targets include NVIDIA Jetson, Raspberry Pi, Qualcomm Dragonwing boards, generic arm64 or x86_64 Linux machines, the Unitree G1 computer, Apple Silicon Macs (beta) and ESP32 microcontrollers (preview). The audience is robotics and embedded teams in manufacturing, energy, medical devices, defense and research who want agent-assisted development rather than hand-built deployment tooling. It sits closer to a robotics deployment stack than to a general ROS distribution, and several pieces are still in preview, beta or planned status.

How do you use Wendy?

  1. 1Install the Wendy CLI
    Run the install script on macOS or Linux (a Windows option is also offered) to get the wendy command on your computer.
    Wendy — Install the Wendy CLI
  2. 2Connect your coding agent
    Add the Wendy plugin to Claude Code or Codex, or connect Cursor, Windsurf or Claude Desktop through the Wendy MCP server.
    Wendy — Connect your coding agent
  3. 3Start a simulated robot
    Ask the agent to create a simulator, for example a Go2 with `wendy vm create go2-sim --profile go2`, and run your app on it.
    Wendy — Start a simulated robot
  4. 4Set up a real device
    Flash WendyOS to a Jetson, Raspberry Pi or Dragonwing board, or install Wendy Agent on a Linux computer you already have.
    Wendy — Set up a real device
  5. 5Ship and operate
    Point `wendy run` at the device over USB-C or the network, then watch logs and metrics and push updates over the air.

Pros and cons

Pros

  • Same project and `wendy run` workflow from simulation to real hardware, reducing reworkAI
  • Designed for coding agents, with a plugin for Claude Code and Codex and an MCP server with 44 toolsAI
  • Simulate robots and drones on a laptop with no hardware, using MuJoCo and ROS 2AI
  • Broad hardware support including Jetson, Raspberry Pi, Qualcomm Dragonwing, Linux and ESP32AI
  • Security guardrails such as mutual TLS, device pinning, declared entitlements and tagged MCP toolsAI

Cons

  • Several features are preview, beta or planned, including the Go2 and G1 sims, Wendy Cloud fleet tools and digital twinsAI
  • Simulation profiles are limited to a few robots, so other machines need custom setupAI
  • Pricing is not published on the homepage, and the main call to action beyond the CLI is talking to the sales teamAI
  • Value depends on adopting WendyOS or Wendy Agent and a container-based app model, which adds a platform dependencyAI
  • Targeted at robotics and embedded teams, so it is heavy for casual hobby experimentsAI

How much does Wendy cost?

Support

A team contact and demo scheduling are offered, plus versioned documentation, installation guides per device and a coding agent setup guide.

Learn more

Integrations

Plugin for Claude Code and Codex, MCP server for Cursor, Windsurf and Claude Desktop. Runs on NVIDIA Jetson, Raspberry Pi, Qualcomm Dragonwing, Linux computers, Unitree G1, Apple Silicon Macs and ESP32. Uses MuJoCo and ROS 2.

Learn more

Features

Laptop simulation of Unitree Go2, G1 and drone formations in MuJoCo with ROS 2, container-based deploys via `wendy run`, live-reload with --watch, OpenTelemetry telemetry, over-the-air updates, Wendy Cloud fleet tools (beta), mTLS security and a 44-tool MCP server.

Learn more

Frequently asked questions about Wendy

  • Does Wendy have an API?
    Yes, Wendy offers an API.
  • How do you use Wendy?
    The walkthrough on this page covers 5 steps: 1. Install the Wendy CLI 2. Connect your coding agent 3. Start a simulated robot 4. Set up a real device 5. Ship and operate.
  • What platforms does Wendy support?
    Wendy is available on MacOS, Windows and Linux.
  • What does Wendy integrate with?
    Plugin for Claude Code and Codex, MCP server for Cursor, Windsurf and Claude Desktop. Runs on NVIDIA Jetson, Raspberry Pi, Qualcomm Dragonwing, Linux computers, Unitree G1, Apple Silicon Macs and ESP32. Uses MuJoCo and ROS 2.
  • What are the limitations of Wendy?
    Several features are preview, beta or planned, including the Go2 and G1 sims, Wendy Cloud fleet tools and digital twins. Simulation profiles are limited to a few robots, so other machines need custom setup. Pricing is not published on the homepage, and the main call to action beyond the CLI is talking to the sales team.

Status

StatusActive
Views0
Outbound clicks0
Added10/7/2026

Platforms

MacOSWindowsLinux

Pricing

Paid

Categories