Waddle Labs offers an API that lets developers connect a robot, type a prompt, and have an agent produce a working policy for the task. The system is built for robotics teams who currently rely on teleoperation data and vision-language-action models to teach new behaviors. Rather than train a large end-to-end model to map pixels and instructions to motor commands, the agent looks through the robot's cameras and then writes code, uses skills, or calls specialist models such as VLAs, producing a program that can be edited afterward.
The launch matters because it reframes robot learning as a code generation problem that scales with frontier LLMs. Planning is handled by the reasoning model rather than the policy, so the agent decomposes long tasks into stages, verifies intermediate outcomes, and re-plans on failure, spawning subagents to coordinate multiple robots when needed. Agents also build a library of parametrized skills like grasping, aligning, and folding, and reuse them across tasks (a fold_grasp skill first created to flip a package was later adapted to fold a t-shirt and a towel). The team pitches four practical uses: direct deployment of the generated program on hardware, supervised data collection, fast baseline policies for new tasks or robots, and autoresearch where an agent runs its own hardware trials against a hypothesis and a budget.
Waddle Labs is built by Hanming Ye and Yiding "Vincent" Song, both Harvard students who, despite wanting to pursue Waddle full-time, are staying at Harvard because their international student visas require it . Their positioning is that policy quality tracks model quality: across a manipulation task suite evaluated on Opus 4.8, Fable 5, and GPT 5.6 Sol, larger models given larger budgets produced better policies, with only Fable 5 and GPT 5.6 at xhigh thinking accomplishing harder tasks like folding a t-shirt . Early access is gated through a request form on the company's site.
Comments (8)
Sign in to join the discussion.
K
Kirill ZavodovJul 27, 2026
20 minutes to write robot code is cool until the robot spends the other 20 minutes knocking over your coffee. what's the rollback story when the agent hallucinates a joint angle?
T
Tomas M.Jul 27, 2026
reminds me of an internal tool we scoped at a big co in 2019 that never shipped because legal freaked about actuator safety. how are you thinking about liability when the agent writes bad motion code?
P
Priya NadkarniJul 27, 2026
the cut from prompt to arm actually moving is way too clean. either your editor is a genius or that b-roll is doing heavy lifting.
O
Obi AlicheJul 27, 2026
harvard math to teaching robots to waddle is a career arc I can respect. curious which robot SDKs you support on day one.
H
hanaJul 27, 2026
the tagline does the whole pitch in four words. wish more launches trusted the reader like that.
V
Vik SahaJul 27, 2026
two founders, one API, a fleet of robots. what's the actual headcount here because this looks suspiciously like a dorm room operation and I mean that as a compliment.
L
Leandra BotelhoJul 27, 2026
physical AI market is smaller than everyone pretends. how many customers actually own a robot arm and a prompt-shaped problem at the same time?
M
Moises AreshJul 27, 2026
the market is small right now, sure, but so was 'websites' in 1994. every warehouse is one API call away from being a customer.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Waddle Labs
Claude Code for robots.
Claude Code for robots.
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Waddle Labs offers an API that lets developers connect a robot, type a prompt, and have an agent produce a working policy for the task. The system is built for robotics teams who currently rely on teleoperation data and vision-language-action models to teach new behaviors. Rather than train a large end-to-end model to map pixels and instructions to motor commands, the agent looks through the robot's cameras and then writes code, uses skills, or calls specialist models such as VLAs, producing a program that can be edited afterward. The launch matters because it reframes robot learning as a code generation problem that scales with frontier LLMs. Planning is handled by the reasoning model rather than the policy, so the agent decomposes long tasks into stages, verifies intermediate outcomes, and re-plans on failure, spawning subagents to coordinate multiple robots when needed. Agents also build a library of parametrized skills like grasping, aligning, and folding, and reuse them across tasks (a fold_grasp skill first created to flip a package was later adapted to fold a t-shirt and a towel). The team pitches four practical uses: direct deployment of the generated program on hardware, supervised data collection, fast baseline policies for new tasks or robots, and autoresearch where an agent runs its own hardware trials against a hypothesis and a budget. Waddle Labs is built by Hanming Ye and Yiding "Vincent" Song, both Harvard students who, despite wanting to pursue Waddle full-time, are staying at Harvard because their international student visas require it . Their positioning is that policy quality tracks model quality: across a manipulation task suite evaluated on Opus 4.8, Fable 5, and GPT 5.6 Sol, larger models given larger budgets produced better policies, with only Fable 5 and GPT 5.6 at xhigh thinking accomplishing harder tasks like folding a t-shirt . Early access is gated through a request form on the company's site.
Comments (8)
20 minutes to write robot code is cool until the robot spends the other 20 minutes knocking over your coffee. what's the rollback story when the agent hallucinates a joint angle?
reminds me of an internal tool we scoped at a big co in 2019 that never shipped because legal freaked about actuator safety. how are you thinking about liability when the agent writes bad motion code?
the cut from prompt to arm actually moving is way too clean. either your editor is a genius or that b-roll is doing heavy lifting.
harvard math to teaching robots to waddle is a career arc I can respect. curious which robot SDKs you support on day one.
the tagline does the whole pitch in four words. wish more launches trusted the reader like that.
two founders, one API, a fleet of robots. what's the actual headcount here because this looks suspiciously like a dorm room operation and I mean that as a compliment.
physical AI market is smaller than everyone pretends. how many customers actually own a robot arm and a prompt-shaped problem at the same time?
the market is small right now, sure, but so was 'websites' in 1994. every warehouse is one API call away from being a customer.