Self-Evolving Coding Agents: From Digital Programs to Physical-World Intelligence

Hongcheng Gao, Jingjing Zhou, Zelin Zheng, Shijia Ge, Jay Zhu, Yazhe Wang, Jianshu Zeng, Xuan Shangguan and 5 others

HexaFuture

Published September 28, 2026 · on the feed September 29, 2026 · ▲ 106 · arXiv 2609.35432

Code & softwareAgentsRobotics & embodied Empty repo arXiv ↗Hugging Face ↗

The abstract

Vision-language-action (VLA) and world-action (WAM) models map observations and instructions directly to robot actions. This directness ties a policy to training: minor layout or viewpoint changes cause failure, and instructions generalize poorly. The root cause lies in representation: task requirements, conditions, progress, and failure recovery are implicitly encoded in action sequences, making them difficult to inspect or revise. Digital coding agents offer a precedent: LLMs call tools, verify results, and revise from feedback as executable code. The same working pattern of explicit state, manageable execution, and revisable procedures underlies generalization and long-horizon execution in the physical world, letting physical experience return as reusable programs, memory, or evidence. We propose Physical Coding, representing task state and execution as code. Code as World records objects, relations, constraints, and progress; Code as Policy organizes planning, verification, recovery, and execution. We build HexaAnything, which calls perception, planning, and control tools, including VLA/WAM policies, and makes in-the-loop decisions from external feedback. Verified traces become data and memory, enabling evolution from tools and Harness to model weights, architectures, and ultimately hardware and task design. On RoboCasa365, HexaAnything improves Composite-Unseen and overall success over XR-1 VLA, and its Harness-trained HexaModel beats the base on every split, indicating code traces internalize physical execution. On PhyBench and a dual-arm AgileX robot, the agent autonomously completes physics experiments and most tabletop tasks, often faster than published results. We observe data, model, and tool self-evolution; future work targets weight internalization, autonomous redesign of architectures, languages, representations, and tasks, and deployment in manufacturing and science.

The Brief

3:10

A short podcast summary of the paper. Written and voiced by AI.

Transcript

Self-Evolving Coding Agents. From Digital Programs to Physical-World Intelligence. By Hongcheng Gao and twelve others, from HexaFuture. Published on the twenty-eighth of September. Its code repository is a placeholder: a readme, and nothing to run yet.

Vision-language-action models and world-action models map observations and instructions straight to robot actions. That directness ties a policy to its training. Minor changes in layout or viewpoint cause failure, and instructions generalize poorly. The authors locate the root cause in representation. Task requirements, conditions, progress and failure recovery are all encoded implicitly in action sequences, where they are difficult to inspect or revise. When a policy fails, there is no written-down notion of what the task required or how far it had got, only a sequence of actions, and nothing explicit that could be corrected directly.

Digital coding agents offer a precedent. Language models call tools, verify the results, and revise from feedback, all as executable code. The authors argue that the same working pattern, explicit state, manageable execution and revisable procedures, underlies generalization and long-horizon execution in the physical world as well, and lets physical experience come back as reusable programs, memory or evidence. The claim is that flexibility comes from that working loop: state you can see, steps you can check, and procedures you can rewrite when a check fails.

Their proposal is Physical Coding: representing task state and execution as code. Code as World records objects, relations, constraints and progress. Code as Policy organizes planning, verification, recovery and execution. What a direct policy hides inside its actions is written out where it can be read and changed.

The system built on this is HexaAnything. It calls perception, planning and control tools, including VLA and WAM policies themselves, and makes in-the-loop decisions from external feedback. Verified traces become data and memory. The authors describe that as the route to evolution, starting from tools and the Harness, and extending to model weights, architectures, and ultimately hardware and task design.

On RoboCasa365, HexaAnything improves success on the Composite-Unseen split and overall, compared with the XR-1 VLA. HexaModel, trained with the Harness, beats its base on every split, which the authors read as code traces internalizing physical execution.

On PhyBench and on a dual-arm AgileX robot, the agent autonomously completes physics experiments and most tabletop tasks, often faster than published results. The authors also report observing data, model and tool self-evolution. Across the three settings, the pattern is that an agent reasoning in code can sit on top of existing robot policies, use them as tools, and wrap a layer of verification and recovery around them.

Much of the ambition is stated as future work: weight internalization, autonomous redesign of architectures, languages, representations and tasks, and deployment in manufacturing and science. The bet underneath is easier to state. A robot's grasp of a task should live in something it can read and rewrite, the way a coding agent's does, rather than inside a sequence of actions it cannot inspect.

Paper Quest · 7 chapters · about 41 min

Play this paper

Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.

Chapter 1 🧩 · The problem

A robot that fails silently, with nothing written down. That is the wall.

You run robot policies that map camera images and instructions straight to actions. A small change in layout or viewpoint, and they fail. Instructions barely matter.

The road ahead

  1. 1 · The problem ~7 min Robot policies that turn images straight into actions break under small changes, and when they fail there is no written record of what went wrong.
  2. 2 · What came before ~3 min
  3. 3 · The key idea ~9 min Write both the world's state and the robot's procedure as programs, call robot policies as tools, and keep checked traces as data to improve.
  4. 4 · Choose your own research ~3 min
  5. 5 · Build the method ~8 min HexaAnything calls perception, planning and control tools in a feedback loop, keeps verified traces, and trains HexaModel on them.
  6. 6 · The experiment ~6 min You’ll guess: On RoboCasa365, did HexaModel, trained with the Harness on verified code traces, beat its base model?
  7. 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Join free to play the whole quest ›

Free, with Google or an email address. Your stars and progress are kept.

KipQuest: the day’s AI research, as podcasts and quests. All papers Android app Privacy Contact Episodes are written and voiced by AI from each paper. Summaries can contain mistakes: the paper is the source.