← All speakers

Bio, Work & Ideas

Sam Bhagwat

Conference affiliation: Founder/CEO · Mastra · 2026

Sam Bhagwat is the co-founder and chief executive of Mastra, an open-source TypeScript framework and platform for building production AI agents. Previously, he co-founded Gatsby Inc., the company behind the React-based web framework Gatsby.

A Stanford graduate, Bhagwat worked as an engineer at PlanGrid and Zenefits before becoming a core Gatsby contributor. In 2018, he and Gatsby creator Kyle Mathews founded Gatsby Inc., where Bhagwat became chief strategy officer. He wrote Modular: The Web’s New Architecture about headless content, e-commerce, web performance, and the organizational challenges of replacing monolithic websites. Netlify acquired Gatsby in 2023.

In October 2024, Bhagwat began building Mastra with fellow Gatsby veterans Abhi Aiyer and Shane Thomas. The company joined Y Combinator’s Winter 2025 batch, giving JavaScript and TypeScript developers tools for agents, workflows, memory, retrieval, evaluation, and tracing. Bhagwat also wrote Principles of Building AI Agents, a practical guide to building agent-based applications.

Mastra released version 1.0 in January 2026. That April, Bhagwat announced a $22 million Series A and the Mastra platform, extending the framework into deployment, evaluation, tracing, and persistent agent memory.

  • Agents and workflows belong together. Agents handle uncertain, iterative tasks; workflows provide explicit sequencing, branching, and recovery. Bhagwat combines them: agents call workflows as tools, workflows invoke agents as steps, and supervisors coordinate specialized agents. His approach to hybrid agent architecture favors adding structure wherever autonomous behavior becomes unreliable.
  • Developer experience determines whether powerful tools get used. Gatsby’s reliance on GraphQL taught Bhagwat that sophisticated abstractions can impose unnecessary conceptual overhead. He opposes agent frameworks that force teams to reason in graph nodes and edges, favoring readable code that makes execution order and control flow immediately visible.
  • Agent harnesses make autonomous work durable. Beyond basic model calls and tool-using loops, Bhagwat emphasizes planning, persistent sessions, background execution, human approvals, context management, and parallel subagents. His analysis of coding-agent architecture examines how these capabilities support longer-running, interruptible, steerable work.
  • Always-on agents need initiative. Bhagwat expects cloud sandboxes, persistent memory, scheduled activity, Slack, and messaging to turn coding assistants into always-on personal agents that notice events and resume work independently. He predicts consolidation among agent products because users have limited attention for assistants that lack frequent or substantial practical value.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

Agents choose what to do next; workflows make dependencies explicit. Combining them lets a system retain flexibility while adding control where reliability requires it.

  • Do agents make workflows obsolete?
    0:00 ↗
  • When provider advice becomes orthodoxy
    2:08 ↗
  • Make execution order readable
    3:39 ↗
  • From architectural patterns to turns and dependencies
    6:20 ↗
  • Add control where behavior becomes unreliable
    9:33 ↗
  • Use agents and workflows inside each other
    11:43 ↗
  • Structured tools, changing toolsets, and nested processes
    12:56 ↗
  • Keep the system that meets its requirements
    14:10 ↗

Key ideas

Scroll to read ↓

Coding assistants are growing into persistent, always-on systems with initiative and learning, but greater capability does not guarantee a lasting place in users’ lives.

  • From a coding assistant to an autonomy spectrum
    0:30 ↗
  • An agent carries state through repeated action
    2:35 ↗
  • A harness keeps work moving
    3:17 ↗
  • Always-on access changes the execution architecture
    5:00 ↗
  • A claw initiates contact and learns from runs
    6:54 ↗
  • Claw capabilities become framework primitives
    8:45 ↗
  • Users pull harnesses into more of their lives
    9:59 ↗
  • Capability competes for limited attention
    11:14 ↗
  • Build for capability growth and selective adoption
    13:30 ↗

References