Code 2025
The 3 Pillars of Autonomy – Michele Catasta, Replit
Overview
This talk explores the concept of autonomy in AI coding agents, particularly for non-technical users. It argues that true autonomy for this audience means offloading all technical decision-making, allowing users to focus solely on their desired outcomes. The presentation redefines autonomy beyond just long runtimes, emphasizing the importance of scoped tasks and robust verification to build powerful and stable agents.
Who should watch
- AI Engineers
- Product Managers
- Builders of AI-powered tools
- Those working on autonomous agents
- Developers aiming to empower non-technical users with software creation
Key takeaways
- Autonomy in AI agents can be categorized into supervised (user remains in control, e.g., Tesla FSD) and a more "whimo" experience where the agent handles all technical aspects.
- The goal for non-technical users is an agent that requires no technical expertise, abstracting away complexity.
- Building autonomous agents relies on three pillars: frontier model capabilities, robust verification at each step, and effective context management.
- Verification is crucial to prevent "painted doors" or broken features, with autonomous testing methods like browser interaction being key.
- Context management can be achieved without extremely long context windows by using techniques like persisting state in the codebase or file system, and employing sub-agent orchestration.
- Sub-agent orchestration improves efficiency and separation of concerns, particularly vital for complex tasks like automated testing.
- Parallelism can enhance user experience by allowing more work to be done concurrently, though managing outputs and potential merge conflicts is a challenge.
- Future development focuses on the core loop acting as an orchestrator for parallelism, enabling on-the-fly task decomposition and mitigating merge conflict issues.
Notable quotes
*We want to empower every knowledge worker to create software.*
*Autonomy should not be basically conflated with long run times.*
*The moment you write a test in script then you can rerun it as many times as you want.*
Unofficial community note. Prefer the recording for nuance.