92%。
这是英伟达最新开源的ASPIRE系统在双臂物体交接任务上的成功率。在它之前,基于Code as Policy范式的方法只能做到20%。4.6倍的提升,不是靠更大的模型、更多的GPU数据,而是靠一套会"记笔记"的机制。
7月1日,英伟达机器人研究主管Jim Fan在X上宣布ASPIRE正式开源,原话很直接:"范式变了。"当机器人完成第100个任务时,它终于不再像完成第1个任务时那样一无所知——这句话点出了当前具身智能最大的痛点:每次都从零开始。
机器人也有了"成长系统"
ASPIRE的全称是Agentic Skill Programming through Iterative Robot Exploration,翻译成大白话:让Agent通过反复试错自己给机器人写技能。它的核心逻辑和Coding Agent如出一辙——程序员用Cursor写代码,跑测试,看报错,改bug,最后把修好的代码提交;机器人用ASPIRE也是一样,只不过它review的不是代码仓库,而是物理世界里的执行轨迹。
具体来说分三步。第一步是执行引擎:机器人每次执行任务时,系统会完整记录感知结果、导航路径、抓取动作、碰撞检测、运动规划的全部输入输出和视觉证据。就像工程师调机器人时会一帧一帧回放视频看哪里出了问题,ASPIRE把这个过程自动化了。
第二步是技能提炼。任务失败后,背后的GPT/Claude会像资深研究员一样分析多模态轨迹:是识别错了?抓取没抓稳?路径规划撞到障碍物了?还是某个恢复动作没接上?找到问题后修改控制程序,重新测试;如果跑通了,就把这次验证过的修复经验沉淀成一条可复用的Skill,写进不断增长的技能库。
举个具体例子:机器人想拿起桌上的收音机,明明识别到了目标,机械臂却死活靠不近。ASPIRE分析后发现,不是视觉识别的锅,而是规划器给出的目标点全落在障碍物的碰撞缓冲区内。于是它总结出一条Skill:遇到规划失败时,尝试从45度、90度、180度等不同角度重新接近目标,直到找到无碰撞路径。这条经验一旦入库,下次不管目标是收音机、微波炉还是马克杯,都能直接调用。
第三步是进化搜索。系统不会只沿着一条修复路径死磕,而是同时生成多条候选控制程序,放进执行环境里跑,再根据幸存者和失败轨迹继续迭代。这本质上是把软件工程里"写代码→跑测试→看trace→改bug"的循环搬进了物理世界。
训练不再是炼权重,而是攒技能
ASPIRE真正激进的地方,在于它对"训练"这件事的重新定义。
过去十年,深度学习的范式非常统一:收集数据→梯度下降→更新模型权重→部署。不管是大语言模型还是具身智能VLA模型,产物都是一堆几十GB几百GB的浮点权重。你打开权重文件,什么也看不懂;模型为什么做出这个决策,很难追溯;想给模型增加一个新技能,最稳妥的办法是重新采集数据、重新训练、重新微调。
ASPIRE给出了另一条路:训练产物不再是权重,而是一个可解释、可积累、可迁移的技能库。训练过程不再是闭门炼丹式的梯度下降,而是Skill Refinement——不断打磨一条条具体的技能。分布式训练也不再是几百张卡同步算梯度,而是一群Agent各自在不同场景练习不同技能,再把经验汇总到同一个技能库里。
这个思路的背后,是Code as Policy范式的成熟。传统VLA模型让神经网络直接输出电机动作,行为完全黑箱化;而Code as Policy让大模型写可执行的机器人控制程序,程序里调用感知模块、规划API和控制原语。代码是白箱的,能被Agent检查、修改、调试、版本化——这是Skill Library能够成立的前提。
论文里的泛化实验很能说明问题。研究团队先在LIBERO-90任务集上不断积累Skill Library,然后直接迁移到从未见过的LIBERO-Pro Long长任务上,中间没有针对新任务继续训练,也没有更新技能库。结果显示,随着技能库越来越丰富,机器人在新任务上的成功率从几乎不会做,一路提升到31%。这意味着Skill Library越厚,机器人迁移到新场景的能力就越强——这正是人类工程师的工作方式:你调过一百个机器人之后,遇到第一百零一个新场景,不会从零开始,而是会调出脑子里的"经验库"。
具身智能的"App Store"时刻?
开源ASPIRE的时机值得玩味。
就在上周,北航机器人所团队创业的航墨科技完成近亿元天使轮融资,主打智能变刚度关节技术;硅羽科技半年连获四轮数亿元融资,做通用空中智能体;VAST完成超10亿元A3轮融资,巨人网络参投,专注AI 3D大模型和通用世界模型。国内具身智能赛道的融资热度丝毫不减。
而在芯片侧,英伟达的竞争对手Etched刚刚拿下50亿美元估值,手里已经握有10亿美元的AI芯片订单。具身智能对算力的需求是无底洞,但光有算力堆不出能用的机器人——这是整个行业的共识。英伟达此时开源ASPIRE,与其说是做慈善,不如说是在建立具身智能时代的"开发者生态"。
想象一下:如果Skill Library的模式跑通了,未来可能会出现一个机器人技能的"App Store"——某家公司训练出了特别擅长开抽屉的Skill,另一家公司打磨出了处理透明玻璃杯的Skill,大家可以交易、组合、复用这些技能,而不是每家都从零开始采集数据、训练模型。这比单纯卖GPU的想象空间大得多。
当然,这个愿景离落地还有距离。ASPIRE目前的实验主要在仿真环境中完成,Sim2Real的迁移仍然是具身智能最大的拦路虎之一。物理世界的复杂度远超过仿真——光照变化、物体材质差异、传感器噪声、机械臂磨损,这些都是代码里难以完全覆盖的变量。但方向是清晰的:让机器人像人类工程师一样在实践中积累经验,而不是每次都重新投胎。
终局判断
AI编程领域过去一年发生的事情,正在具身智能身上重演。
2025年大家还在比谁的模型补全代码更准;2026年,Cursor、Claude Code、Devin这些产品已经开始跑完整的工程循环——理解需求、写代码、跑测试、看报错、修bug、提交PR。核心竞争力从"单次生成质量"转向了"闭环迭代能力"。
具身智能正在走同样的路。比谁的VLA模型在benchmark上分数高是一回事,能不能在真实环境里持续学习、积累经验、不犯重复错误是另一回事。ASPIRE的价值,在于它把机器人从"每次都从零开始的小白"变成了"会记笔记、会复盘、会成长的学徒"。
Jim Fan说"范式变了",不是夸张。当训练的目标从产出一组权重变成沉淀一个可积累的技能库,当分布式训练从同步梯度变成多Agent并行探索汇总经验,当机器人的能力提升不再只靠炼大模型而是靠Skill Library越积越厚——具身智能的游戏规则确实在改写。
92%的双臂交接成功率是一个漂亮的数字,但更值得记住的是数字背后的方法论转变。毕竟,人类能从手工作坊走到工业革命,靠的从来不是某一代人天生更聪明,而是每一代人都能站在前人的肩膀上——知识和技能的可积累、可传递,才是文明进步的核心。机器人,终于也开始学会这件事了。
92%.
That's the success rate of Nvidia's newly open-sourced ASPIRE system on dual-arm object handover tasks. Before ASPIRE, methods based on the Code as Policy paradigm could only manage 20%. That 4.6x improvement didn't come from bigger models or more GPU training data -- it came from a mechanism that knows how to "take notes."
On July 1, Nvidia's robotics research lead Jim Fan announced ASPIRE's open-source release on X, putting it bluntly: "The paradigm has changed." When a robot completes its 100th task, it's finally no longer as clueless as it was on task number one -- a line that cuts straight to embodied AI's biggest pain point: starting from scratch every single time.
Robots Get a "Leveling System"
ASPIRE stands for Agentic Skill Programming through Iterative Robot Exploration. In plain English: let the Agent write robot skills through trial and error, all by itself. The core logic is identical to how Coding Agents work -- a programmer uses Cursor to write code, runs tests, checks errors, fixes bugs, and finally commits the working code; robots using ASPIRE do the same thing, except instead of reviewing a code repository, they're reviewing execution trajectories in the physical world.
It breaks down into three steps. Step one is the Execution Engine: every time the robot performs a task, the system fully records all inputs, outputs, and visual evidence -- perception results, navigation paths, grasping motions, collision detection, motion planning. Just like engineers debug robots by replaying video frame by frame to spot problems, ASPIRE automates this process.
Step two is Skill Distillation. After a failed task, the underlying GPT/Claude analyzes the multimodal trajectory like a senior researcher: was it a misrecognition? A weak grasp? Did the path planner hit an obstacle? Or did a recovery motion fail to chain properly? After identifying the problem, it modifies the control program and retests; if it passes, that verified fix is crystallized into a reusable Skill and added to the ever-growing skill library.
A concrete example: a robot tries to pick up a radio on the table. It correctly identifies the target, but the arm can't get close no matter what. ASPIRE analyzes and discovers the problem isn't visual recognition -- it's that the planner's target points all land inside the obstacle's collision buffer zone. So it distills a Skill: when planning fails, try approaching the target from different angles -- 45 degrees, 90 degrees, 180 degrees -- until a collision-free path is found. Once that experience enters the library, it can be called upon next time regardless of whether the target is a radio, a microwave, or a mug.
Step three is Evolutionary Search. The system doesn't hammer away at a single repair path; it generates multiple candidate control programs simultaneously, runs them in the execution environment, then iterates further based on survivors and failure trajectories. This is essentially porting the software engineering loop of "write code -> run tests -> inspect traces -> fix bugs" into the physical world.
Training Isn't About Refining Weights Anymore -- It's About Accumulating Skills
What makes ASPIRE truly radical is its redefinition of what "training" means.
For the past decade, deep learning has followed a single paradigm: collect data -> gradient descent -> update model weights -> deploy. Whether it's large language models or embodied AI VLA models, the output is tens or hundreds of gigabytes of floating-point weights. Open a weights file and you can't read a thing; it's nearly impossible to trace why a model made a particular decision; if you want to add a new capability, the safest bet is to collect new data, retrain, and fine-tune from scratch.
ASPIRE charts a different path: the product of training is no longer weights, but an interpretable, accumulable, transferable skill library. Training is no longer black-box gradient descent alchemy -- it's Skill Refinement, continuously polishing concrete skills one by one. Distributed training is no longer hundreds of GPUs synchronizing gradients; it's a swarm of Agents practicing different skills in different scenarios, then pooling their experiences into a shared skill library.
Behind this approach lies the maturation of the Code as Policy paradigm. Traditional VLA models have neural networks output motor actions directly, making behavior a complete black box. Code as Policy has LLMs write executable robot control programs that call perception modules, planning APIs, and control primitives. Code is white-box -- it can be inspected, modified, debugged, and versioned by Agents. That's the prerequisite that makes a Skill Library possible.
The generalization experiments in the paper tell the story. The research team built up the Skill Library on the LIBERO-90 task set, then directly transferred it to the never-before-seen LIBERO-Pro Long horizon tasks -- no additional training, no skill library updates. The results show that as the skill library grew richer, the robot's success rate on novel tasks climbed from near-zero to 31%. This means the thicker the Skill Library, the stronger the robot's transfer to new scenarios -- exactly how human engineers work: after tuning a hundred robots, you don't start from zero on the hundred-and-first; you pull from the "experience library" in your head.
Embodied AI's "App Store" Moment?
The timing of ASPIRE's open-source release is worth pondering.
Just last week, Hangmo Tech (spun out of Beihang University's Robotics Institute) closed a nearly 100 million RMB angel round for its intelligent variable-stiffness joint technology; Siyu Technology raised hundreds of millions across four rounds in six months for universal aerial agents; VAST closed a 1+ billion RMB Series A3 led by Giant Network, focusing on AI 3D foundation models and general world models. China's embodied AI funding shows zero signs of cooling.
On the chip side, Nvidia competitor Etched just hit a $5 billion valuation with $1 billion in AI chip orders already in hand. Embodied AI's appetite for compute is bottomless, but everyone in the industry agrees: compute alone won't produce usable robots. Nvidia open-sourcing ASPIRE now is less about charity and more about building the "developer ecosystem" for the embodied AI era.
Imagine: if the Skill Library model works, the future could bring an "App Store" for robot skills -- one company trains a Skill particularly good at opening drawers, another polishes a Skill for handling transparent glassware, and everyone can trade, combine, and reuse these skills instead of every company collecting data and training models from scratch. That's a far bigger vision than simply selling GPUs.
Of course, that vision is still some distance from reality. ASPIRE's experiments were conducted primarily in simulation, and Sim2Real transfer remains one of embodied AI's biggest roadblocks. The physical world is vastly more complex than simulation -- lighting changes, material differences, sensor noise, mechanical wear -- variables that code can never fully cover. But the direction is clear: make robots accumulate experience like human engineers in practice, rather than being reborn from scratch every time.
Endgame Assessment
What happened in AI coding over the past year is now repeating itself in embodied AI.
In 2025 everyone was competing on whose model completed code more accurately; by 2026, products like Cursor, Claude Code, and Devin are already running full engineering loops -- understanding requirements, writing code, running tests, reading errors, fixing bugs, submitting PRs. The core competitive advantage has shifted from "single-shot generation quality" to "closed-loop iteration capability."
Embodied AI is walking the same path. Whose VLA model scores higher on benchmarks is one thing; whether it can continuously learn, accumulate experience, and avoid repeating mistakes in real environments is quite another. ASPIRE's value lies in transforming robots from "newbies starting from zero every time" into "apprentices who take notes, review, and grow."
When Jim Fan says "the paradigm has changed," it's no exaggeration. When the goal of training shifts from producing a set of weights to depositing an accumulable skill library, when distributed training shifts from synchronized gradients to multi-Agent parallel exploration pooling experience, when a robot's improvement no longer relies on training bigger models but on a Skill Library growing thicker and thicker -- the rules of embodied AI are genuinely being rewritten.
That 92% dual-arm handover success rate is a beautiful number, but what's more worth remembering is the methodological shift behind it. After all, humanity went from artisan workshops to the Industrial Revolution not because any single generation was born smarter, but because each generation could stand on the shoulders of those before them -- the accumulation and transmission of knowledge and skills is the core of civilization's progress. Robots, finally, are starting to learn that too.
Nvidia ASPIRE · Embodied AI · Robot Skill Library · Code as Policy · Skill Library · Jim Fan · Continuous Learning Paradigm