Skip to content
← All articles

Code fell fast because it was verifiable; Warp wants chemistry next

Warp CTO Manohar, until weeks ago a Meta VP, argues frontier AI needs verifiable physical feedback loops to keep improving, while conceding closed labs will likely keep leading on capability.

ManoharYann LeCunMark ZuckerbergWarpMetaFoundation ModelsRoboticsHealthcare AIOpen SourceNew
YouTube upload date not supplied
Code fell fast because it was verifiable; Warp wants chemistry next

Recorded 23 October 2026 · 85 min

Manohar left a VP role at Meta a few weeks ago to become founder and CTO of Warp. His core argument is that AI progress tracks verifiability. Code and math fell quickly because outcomes can be checked automatically, while the physical world offers no equivalent loop. Warp is his attempt to build one, starting with wet-lab automation for small-molecule drug discovery. The host, Siddharth of Neon, is an investor in the company.

The discussion tests how far that thesis reaches. Manohar accepts that the frontier's general intelligence keeps absorbing application-layer work. He argues open ecosystems win the long arc, yet closed models will likely keep leading on capability, and he defines sovereignty as capability rather than ownership. The unresolved tension is whether chemistry, where verification takes a week or more, can follow the curve that code did.

  1. The missing physical loop — ▶ 4:56

    Manohar says the next bottleneck is not a bigger model but learning from reality at the atomic level. A model forms a hypothesis, acts on a physical instance, observes the result and learns, and that loop "hasn't been built yet." Code, math, chat, enterprise agents and personal assistants were all built without atoms in the loop. He frames leaving Meta as a choice of problem over position. His stated conviction is that the most learning will come from models acting in physical space, with video-to-sim and real-to-sim-to-real gaps as the current obstacles.

  2. Verifiability explains coding's speed — ▶ 8:34

    Models went from early promise on code to people coding "in English" within about a year. Manohar attributes this to verifiable loops: reinforcement learning rollouts can be unrolled, code can be compiled, and Lean lets math proofs be checked. Progress then becomes "a matter of computation" plus self-play-style improvement. The real world lacks this, and its loop is bottlenecked by humans, atoms and long lead times. Editorial inference: domains where verification can be automated are the likeliest to move next.

  3. Why wet labs stall learning — ▶ 9:47

    A designed small molecule must be made in a wet lab, following roughly 10 steps, by a chemist who works about 8 hours and then sleeps. Few chemists can run the precision equipment. Results arrive after a week or two as LCMS spectrography and may not be digitized. In materials science, a 1% change in composition yields a different material, forcing repeats. His counterfactual is foundation models for target selection, robots plus humans running 24x7, and riskier hypotheses, which would turn a data-poor domain into a data-rich one.

  4. Beyond personal assistants — ▶ 12:34

    Manohar does not call personal assistants trivial, since he uses them daily, but says shopping and travel planning scratch the surface and may not be AI's ultimate benefit. What changed his mind is math proofs he calls "almost field medal quality," though he concedes he is not a math expert and a debate is raging. His inference is that enough compute, a good starting seed and a verifiable domain can yield discovery. He hedges that models may only help humans discover rather than discover alone.

  5. Harnessing a growing nucleus — ▶ 15:45

    The frontier's expanding capability is real, Manohar says, because each new model simplifies customization built on the last. His test for application builders is whether cost, efficiency and speed improve with each model. Teams should avoid an "impedance mismatch" where every new model forces re-engineering, and should compete where they hold unique data and iteration speed from subject expertise. The alternative is betting on a new paradigm, such as world models whose simulations serve as RL rollouts. He treats the two as an explore-exploit balance that must not be confused.

  6. Open ecosystems, closed frontier — ▶ 19:08

    Open ecosystems win the long arc, he argues, through exploration parallelism: people take parts of a full engine, innovate, and others learn from it. PyTorch lacked TensorFlow's feature parity at the start but grew developers exponentially as its core improved. Open weights are not open source, though, since users cannot pretrain from random weights. Closed models will probably lead in capability, reliability and readiness, while open weights offer control and sovereignty at a capability cost. He also argues cybersecurity needs frontier models in the loop, so safety must be navigated before fully opening.

  7. Distribution versus captured value — ▶ 24:11

    Siddharth argues closed ecosystems such as Apple and Tesla capture the most economic value. Manohar concedes that depends on the metric: Android runs on more devices, but market cap favors closed. If a technology's core value is democratization, open wins; if it is easy, reliable packaging, closed wins, and he would accept closed for commoditized technology. He endorses the host's summary that open gets distribution while the frontier captures value. Closed models stay ahead through compounding loops, he says, unless a new paradigm overturns the current one.

  8. Paradigm shifts reset leaders — ▶ 27:38

    Speech was considered nearly solved in the 1990s using MFCCs, and computer vision relied on handcrafted features until AlexNet in 2012. Manohar calls LLMs to VLMs to VLAs to world action models iterative improvements, not paradigm shifts, which would force a restart with new scaling laws, datasets and skills. His evidence for speed: a GPU he assembled on his desk at Facebook, because data centers held only CPUs, has roughly 20 times its flops in a phone about 12 years later. He frames decisions as "what if" questions: 10x better hardware, learning or serving cost.

  9. Sovereignty as capability — ▶ 31:32

    Sovereignty driven by imitation fades once economics favor the better product, Manohar argues, while sovereignty framed as innovation sustains motivation, as in the Cold War. He would measure it by whether a country can build what it needs at every layer: a sovereign model is meaningless without hardware, and hardware without adoption loops. Siddharth counters that India's closed era pre-1991 gave consumers little choice. Manohar, saying he is not an economist, replies there is no clear equilibrium. He proposes serving users globally and enabling healthy participation, drawing sector-specific lines, with autonomous-vehicle security as a case for closure.

  10. Launching on X — ▶ 39:36

    Frontier launches have moved to X because it lets companies read the first reactions and adapt in real time, he says. He cites a recent Meta launch where inference problems were found and fixed publicly, shifting the conversation away from model quality. His caveat is that "perception leads reality, but reality catches up," so X fine-tunes a launch rather than defines it. Math results launched where the math community was absent produced a one-sided debate, and the real requirement is "meat on the bone."

  11. Spot, learn, leap, deliver — ▶ 44:02

    Manohar's decision cycle is to spot a bottleneck, learn from experts with humility, take a leap without second-guessing, build with a high bar for talent, and deliver something real people use, not a demo, paper or patent. In robotics, hours with experts convinced him that dexterous manipulation is the key bottleneck and "hand is the ultimate frontier." He says a chatbot could state that conclusion, but not convey the assumptions experts live with. He admits his 2009 bet that robotics would be mainstream by 2014 was wrong by more than a decade.

  12. Disagreeing with LeCun — ▶ 49:05

    Yann LeCun, Manohar says, has held for two decades that existing paradigms have limits, and he favors giving research labs freedom and resources and leaving them alone. Manohar disagrees: he prefers multidisciplinary teams of researchers and engineers with audacious goals and milestones, and says both models can produce strong results. From Mark Zuckerberg he learned to simplify a space to its core after mastering its detail, citing the Instagram acquisition that staff doubted. He judges leaders by their frameworks rather than outcomes, and says Zuckerberg's boldness could push products out faster than they are ready.

  13. Making discovery compound — ▶ 1:01:19

    Kevin Weil, formerly OpenAI's CPO, told Manohar that wet-lab automation was the bottleneck in a data-poor domain, and Saul Rosenberg, now chief science officer, argued for a small-molecule focus. Manohar describes small molecules as a small part of the discovery pipeline. His success metric goes beyond faster drugs to new compounds per week per chemist, so lead optimization is not chemistry-bound. The ultimate goal is to "make discovery compound" with each experiment run by humans, robots or both. He chose this start because physical intelligence is rudimentary but maturing fast.

  14. Making the elephants dance — ▶ 1:06:53

    Asked how Warp will move pharma at its pace, Manohar says the answer is solving a fundamental bottleneck so the whole industry gains an incentive to do more. He expects foundation models, having penetrated code and math, to eventually reach chemistry and biology. He names the obstacles himself: a geopolitical question over whether to onshore wet labs, incumbents that prefer someone else take the risk, and whether to add antibody data to small molecules. He offers no resolution, only the stated aim of "scientific super intelligence" built with partners, existing companies and new ones.

The open question. Code improved quickly because verification was nearly instant and automatic. Wet-lab verification, by Manohar's own account, takes a week or two, needs scarce operators, and may not be digitized. Can round-the-clock robots with humans in the loop shrink that cycle enough to produce reinforcement-learning-scale data? The conversation offers a metric, compounds per week per chemist, but no baseline, no target and no evidence yet that the physical loop will compress the way the code loop did.

Watch the full video at https://www.youtube.com/watch?v=d78Buj5rWuA.

Add a private note.

Comments ()

Share this article

Search the library

Search titles and public subject metadata.