← All speakers

Bio, Work & Ideas

Michele Catasta

Conference affiliation: Replit · 2025

Michele Catasta is the president and head of AI at Replit, where he leads development of Replit Agent, software designed to let people without programming expertise build working applications. His career spans semantic search, graph-machine-learning research, Google’s PaLM models, and increasingly autonomous coding systems.

Catasta co-founded the semantic-web search engine Sindice, earned a computer science doctorate at EPFL, and conducted research at EPFL and Stanford, including a machine-learning postdoctoral fellowship under Jure Leskovec. He co-authored the Open Graph Benchmark, which established standardized datasets and evaluation protocols for graph machine learning.

At Google X and Google Labs, he led applied research on language models and source code and contributed to PaLM and PaLM 2. He joined Replit as vice president of AI in June 2023, laying out an agent-centered vision for software development in which models use programming tools, observe execution, and recover from errors.

His early Replit work included Replit Code v1.5, a compact, openly released coding model trained on filtered, permissively licensed data and optimized for practical inference. In 2024, he served as principal investigator on research into automated code repair and led the initial launch of Replit Agent. Later generations expanded the system’s ability to build, test, and coordinate substantial software projects.

  • Autonomy without technical supervision. Catasta defines meaningful autonomy by the amount of useful work an agent completes without requiring users to make engineering decisions. Users should control what they want built; agents should handle implementation. Long runtimes alone prove nothing.
  • Verification against convincing failures. Generated applications often look finished while buttons, databases, or integrations remain broken. Catasta combines static analysis, execution, API checks, logs, and Playwright-based autonomous testing to detect these failures. Agent-generated browser tests also become reusable regression coverage.
  • Focused context and agent-directed orchestration. Plans and intermediate state can live in files instead of filling a model’s context window. Specialized subagents isolate noisy work such as browser testing, return concise results, and make parallel execution practical without requiring nontechnical users to coordinate tasks or resolve conflicts.
  • Continual learning for agents. Catasta argues that application teams can improve agents even without owning the underlying model weights. Better harnesses, evaluation, production feedback, verification, and continual learning turn real-world failures into opportunities to improve software-building systems.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Making AI assistance a default feature requires more than a capable model: Replit’s approach connects curated training data, compact architecture, fast inference, and responsive deployment.

  • Making better programming tools available to everyone
    0:16 ↗
  • From Ghostwriter to default AI assistance
    2:23 ↗
  • Putting inference inside the application
    5:14 ↗
  • A small model with an interactive latency budget
    6:17 ↗
  • Spend more during training to serve a smaller model
    8:58 ↗
  • Curate the corpus, then reuse it
    10:36 ↗
  • Pack more code into a compact architecture
    14:05 ↗
  • Evaluate generated programs by running them
    15:27 ↗
  • Adapt the model to the code users actually write
    17:30 ↗
  • Optimize both generation and capacity startup
    19:52 ↗
  • Let the community extend the model
    22:11 ↗
  • Give completion the surrounding syntax
    23:50 ↗

Key ideas

Scroll to read ↓

A coding agent for nontechnical users must take technical decisions, verify its own work, and preserve intent across long tasks—without making the user its supervisor.

  • Who handles the technical decisions?
    0:00 ↗
  • Autonomy is a scope of responsibility
    3:02 ↗
  • Capability, local correctness, and global coherence
    7:00 ↗
  • Testing must find the painted doors
    8:25 ↗
  • Gather feedback at the right layer
    11:12 ↗
  • Generate executable tests, not just browser actions
    13:21 ↗
  • Long trajectories do not require keeping everything in context
    15:11 ↗
  • Use subagents to separate concerns
    17:00 ↗
  • Keep browser observations out of the coding loop
    18:23 ↗
  • Spend compute to give the user time back
    19:46 ↗
  • Let the code loop orchestrate the work
    23:13 ↗

References