WhoBuilt

Now Anyone Can Code: How AI Agents Can Build Your Whole App

Oct 18, 2024· 37 min· 95K views·Watch on YouTube

Speakers

Replit co-founder and CEO Amjad Masad joins YC’s The Lightcone with Gary, Jared Friedman, and Diana Hu to demo Replit Agent and discuss how AI agents build software.

From a prompt to a working app

Masad asks Replit Agent to create a mood tracker that records daily mood alongside coffee, alcohol, and exercise. The agent proposes a plan, selects Flask, vanilla JavaScript, and Postgres, then builds an app with a history view and activity trends. It also generates sample data and deploys the result, while asking Masad to do some quality checks.

How the agent works, and where it fails

Masad describes a multi-agent system using Claude Sonnet 3.5 for coding, GPT-4o for some tasks, and in-house tools for embeddings and code retrieval. The system combines text retrieval with lookups for code functions and symbols, and manages which memories enter the agent’s context. Masad says the agent can make mistakes or get stuck, so users may need to test, debug, or edit the code themselves.

Coding knowledge still matters

Masad describes the agent as a coworker that can make errors and benefit from human guidance. He argues that learning to code helps people direct agents and solve problems the agent cannot handle. He compares incremental learning through personal software projects to earlier generations learning through Myspace pages and GeoCities sites.

What people build and what comes next

Masad shares examples including a personal map for storing life memories and a Stripe coupon tool built in minutes. He says Replit Agent could help people move beyond the limits of no-code tools and eventually work with existing codebases. Planned directions include background work that returns a pull request, human experts joining when an agent gets stuck, and more user control through previews of proposed code changes.

Building the product as a team

Masad says Replit became more productive after flattening its organization and focusing on a few priorities. For the agent launch, teams across AI, the IDE, package management, and design formed an Agent Task Force. They reviewed live product runs twice a week to find failures, set priorities, and make rapid changes; Masad says reliability and support for more technology stacks are key next steps.

Takeaways

  • Treat an AI coding agent as a coworker: review its output, test the app, and be ready to debug.
  • Learn enough coding to guide agents, understand their changes, and handle problems they cannot solve.
  • For code retrieval, combine semantic search with knowledge of functions and symbols in the codebase.
  • Give product teams frequent hands-on reviews of real user flows so they can prioritize concrete failures.
  • Offer experienced users previews and control over proposed changes, including code diffs and package installations.

Mentioned in this talk

Search inside this talk

What was claimed 12

Show all 12 facts

Related talks

Now Anyone Can Code: How AI Agents Can Build Your Whole App, Amjad Masad, Diana Hu, Jared Friedman, Gary · WhoBuilt