Engineering brief

LLMs as Robot Brains: Why Robotics R&D May Be Investing in the

Y Combinator3 min read · saves 27 min

At a glance

The brief is enough

Relevance
Practical value
Radar
Time horizon
This year
Warnings
None

Frontier LLMs are beating specialized robot models by writing code instead of learning from robot data. Two startup founders explain why the fastest path to general-purpose robots may bypass domain-specific training entirely.

Domain-specific robot models may become obsolete faster than most teams realize. Budget accordingly.

Watch if you are evaluating whether to invest in domain-specific robot models or bet on general-purpose LLMs.

Summary

The shift. A growing group of robotics researchers and startup founders now argue that general-purpose language models—not models fine-tuned specifically on robot data—may become the most effective way to control robots. This idea, which MIT Professor Philip Isola recently called the era of "robot-use agents," is built on a simple observation: frontier LLMs are already good at writing code, and controlling a robot is fundamentally a code-generation problem.

The historical arc. The conversation traces the lineage from RT-2, which fine-tuned a language model to output end-effector poses directly, through code-as-policies methods that let LLMs write Python functions to control robots one-shot, to the current generation where models like Astra can write complex policy graphs with built-in failure handling. The key architectural insight: early VLA (vision-language-action) models were essentially transductive—mapping inputs to actions without intermediate reasoning—while modern LLMs can chain-of-thought, write code, and use tools, which is far more sample-efficient.

The data lesson. Both founders argue forcefully for the bitter lesson: scale and diverse data beat domain-specific engineering. Waddle Labs is building a harness that lets LLMs control robots by treating robot APIs as tools, then consolidating successful traces into fast, reusable skills. RoboCurve evaluates every approach—LLMs, VLAs, world action models—and reports that current LLMs often match or exceed specialized models on spatial reasoning tasks, especially when given a good harness.

The latency bottleneck. Directly querying a frontier model for every robot movement introduces unacceptable latency. Astra's response times, while improving 2x per month, are still too slow for real-time control at useful throughput. The proposed solution: use the LLM to generate a deterministic code path once, with sensory checkpoints where a smaller VLM intervenes for failure detection and variation. This mirrors the sleep-and-compression cycle in biological intelligence—fast in-context learning to gather experience, then consolidation into faster policy weights.

The organizational blind spot. Most teams assume that robotics progress depends on better robot data collection and more VLA training. Both founders suggest the opposite: the fastest path may be to ignore robot data entirely and bet on frontier LLMs trained on computer-use traces, code, and images. This flips the standard R&D allocation argument—companies like Figure or Tesla should still fine-tune at scale, but for everyone else, LLM-as-controller may be the smarter bet by an order of magnitude.

My take

I buy the bitter lesson argument: domain-specific data is a crutch when you can access the entire internet's worth of code and visual data through a general model. But I'm skeptical of the 'general-purpose robots in two years' timeline. That's the kind of prediction that sounds bold until you realize six months were lost to latency alone. The real insight here is organizational: the teams that will win are the ones that build thin harnesses around frontier models and invest in data consolidation pipelines, not the ones racing to collect more robot demos. I'd bet on the harness, not the model.

What to do with this

  1. Ask your robotics or automation team: what percentage of our R&D budget goes to fine-tuning vs. building a better harness around frontier models?
  2. Evaluate whether your robot data pipeline could be replaced or augmented by computer-use traces or CAD interaction data.
  3. Run a small experiment: use Astra or a comparable frontier model to control a single robot arm for 3 simple tasks. Measure latency and success

Watch the video

This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.

Related breakdowns

Get TL;DW

Too Long; Didn't Watch.

A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.

Free. Weekly. No hype.

Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.