ASPIRE: Can Code Refinement Make Robot Manipulation Generalize?

Can a robot improve by remembering how it fixed its own code? This episode explains how NVIDIA's ASPIRE turns robot execution feedback into reusable manipulation skills, and what its evaluations actually establish. We cover three questions: how fine-grained traces support targeted program repair; why a persistent skill library changes the meaning of continual learning; and how task-specific refinement differs from transferring experience to unfamiliar problems. The analysis separates the June 2026 paper from the October 2026 open-source update and its reported near-saturated benchmark results. ([github.com](https://github.com/NVlabs/ASPIRE)) Experiments span LIBERO-Pro and Robosuite simulation, household mobile manipulation, and skill transfer to a physical bimanual YAM robot. ([arxiv.org](https://arxiv.org/html/2607.00272v1)) We connect the method to Voyager, CaP-X, and the emerging combination of coding agents with learned motor primitives. The central limitation is evaluation scope: success after debugging a known task does not establish broad competence on unseen physical task families. The released BEHAVIOR workflow makes that distinction especially concrete. ([raw.githubusercontent.com](https://raw.githubusercontent.com/NVlabs/ASPIRE/main/.claude/skills/iterative-debugging/behavior/SKILL.md)) For researchers building robot learning systems, the practical question is compelling: what should a failed execution teach the next program?