HexaShell: A Thin Harness for Exploring the Limits of VLM Agents as Robot Coding Agents

Hongcheng Gao, Alex Zhou, Jay Zhu, Zelin Zheng, Shijia Ge, Xiping Li, Di Wu, Yazhe Wang and 8 others

HexaFuture

Published October 16, 2026 · on the feed October 19, 2026 · ▲ 118 · arXiv 2610.23479

AgentsRobotics & embodiedCode & software Full code arXiv ↗Hugging Face ↗

The abstract

Agents built on vision language models (VLMs) now compete with learned policies on robot manipulation leaderboards. We ask how far a coding agent can go when it controls a robot instead of a computer, and where it stops. Our system, HexaShell, keeps the harness thin: it only turns the agent's commands into robot motion. The agent drives a robot with two arms through one command line. It sees three RGB cameras and knows their calibration. After each failed attempt, the agent reads the log, finds the cause, and writes or fixes small programs called tools. In this way it keeps what it learns as code, as a coding agent does when it fixes a failing test. The tools may use only what the robot observes. They use triangulation to find where objects are, relative to each other and to the gripper. If two cameras see the same point, the point lies where the two camera rays meet. If a point lies on a known plane, such as the table or the top of a block, it lies where its ray meets that plane. When the head camera is not enough, the robot moves a wrist camera to get a second view. We build the tools on only ten layouts of one seed per task, then freeze them and test them on ten new layouts of the same seed. We use Codex with GPT-6-Astra at medium reasoning effort. On all 42 RoboDojo tasks, HexaShell reaches a success rate of 39.7% and a progress score of 48.0, averaged in the same way as the leaderboard. This is a new state of the art on RoboDojo. The limit is contact, not reasoning: pushing reaches 92.5% and memory tasks 65.0%, but tight insertion only 8.3%. When the agent fails, it usually sees the failure but cannot make the motion work. We open source the tools evolved so far at https://github.com/HexaFuture/HexaShell.

The Brief

3:11

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

Transcript

HexaShell. A Thin Harness for Exploring the Limits of VLM Agents as Robot Coding Agents. By Hongcheng Gao and fifteen others, from HexaFuture. Published on the sixteenth of October. Its code repository is worked out: about three hundred source files, with a readme and a licence.

Agents built on vision language models now compete with learned policies on robot manipulation leaderboards. That raises a plain question, and the paper asks it directly. A coding agent is used to controlling a computer. How far can it go when what it controls is a robot instead, and where does it stop? The paper is framed as an exploration of that limit, so finding the stopping point matters as much as the score.

HexaShell answers by keeping the harness thin. Its only job is to turn the agent's commands into robot motion. Everything else is left to the agent, which works the way a coding agent works on software. After each failed attempt, it reads the log, finds the cause, and writes or fixes small programs the authors call tools. What it learns is kept as code. The analogy the authors draw is to a coding agent fixing a failing test: the failure is read, the cause is found, and the fix stays in the codebase for next time.

The agent drives a robot with two arms through a single command line. It sees three RGB cameras and knows their calibration. The tools it writes may use only what the robot observes, and they locate objects by triangulation, both relative to one another and relative to the gripper. The geometry is simple enough to say in two sentences. If two cameras see the same point, the point lies where the two camera rays meet. If a point lies on a known plane, like the table or the top of a block, it lies where its ray meets that plane. And when the head camera is not enough on its own, the robot moves a wrist camera to get a second view.

The protocol is set up to test whether the tools generalize rather than memorize. Tools are built on only ten layouts of one seed per task. They are then frozen, so no further fixes are allowed, and tested on ten new layouts of that same seed. The agent itself is Codex, running GPT-6-Astra at medium reasoning effort.

Across all forty-two RoboDojo tasks, HexaShell reaches a success rate of thirty-nine point seven percent and a progress score of forty-eight, averaged the same way the leaderboard averages them. That makes it a new state of the art on RoboDojo, achieved with a harness that does nothing but relay commands.

The breakdown by task type is where the paper's real finding lives, because the average hides a wide spread. Pushing reaches ninety-two point five percent. Memory tasks reach sixty-five percent. Tight insertion reaches only eight point three percent. The failures have a pattern, too. When the agent fails, it usually sees the failure. What it cannot do is make the motion work. Perception and diagnosis hold up, and the physical execution is what gives way.

HexaShell's own summary is the line to carry away: the limit is contact, not reasoning. A coding agent with cameras and a command line can diagnose, locate and plan well enough to lead the leaderboard, and it still cannot reliably complete a tight insertion. That puts the open problem squarely in contact-rich motion. The tools evolved so far are open source, so others can start from them.

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 coding agent is at home in a repository. Now hand it a robot and see where it stops.

You have a capable coding agent and a robot with two arms, watched by three calibrated RGB cameras. Robot leaderboards have been led by learned policies trained on large sets of demonstrations.

The road ahead

  1. 1 · The problem ~7 min A coding agent is good at fixing software, but a robot needs positions in the world, and the agent only sees camera pixels.
  2. 2 · What came before ~3 min
  3. 3 · The key idea ~8 min Keep the harness thin, let the agent turn each failure into small measuring tools kept as code, and have those tools triangulate positions from calibrated cameras.
  4. 4 · Choose your own research ~3 min
  5. 5 · Build the method ~8 min Each development layout is tried, failures are diagnosed and turned into tool fixes, then the tools are frozen and scored on new layouts.
  6. 6 · The experiment ~7 min You’ll guess: HexaShell set a new state of the art on RoboDojo. Which of these kinds of task was its weakest?
  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.