How Amp Ships 50 Times a Day With AI Agents
Show notes
Amp ships to production around 50 times a day with AI agents, but the change that makes their team ship faster isn't AI at all. Dario Hamidi, AI engineer at Amp, makes the case that pull requests are holding your team back, and explains what replaces them.
In this video, we cover:
- Why Amp works without pull requests or feature branches, and how to try it with your own team
- Agent permissions, approval fatigue, and building environments where you can trust agents
- Orbs: remote agent execution, parallelism, and multiplayer sessions
- Short-lived credentials and workload identity federation for cloud agents
- Triaging 60+ bug reports a day with agents without frying your brain
For engineers and engineering leads who want to ship faster with AI agents and are ready to question the workflows they've always used.
Timestamps:
00:00:00 - Is It Time to Kill the Pull Request?
00:00:45 - What Happens If Every PR Gets Auto-Closed Tomorrow
00:05:04 - Pull Requests Were Built for Strangers, Not Teammates
00:07:20 - Does Dropping PRs Hurt Quality at Scale?
00:08:53 - Agent Permissions: Why No Default Makes Everyone Happy
00:12:42 - Don't Juggle Knives: Building Environments You Can Trust
00:14:56 - The Hidden Hard Parts of Cloud Agents
00:16:39 - What's an Orb? Remote Agent Execution Explained
00:19:10 - How to Give Agents Credentials Without Leaking Secrets
00:22:51 - Why Orbs Live Forever (and Multiplayer Orbs)
00:25:49 - The State Management Problem Nobody Talks About
00:29:22 - When Will Everyone Have Remote Dev Environments?
00:32:23 - Orbs That Spawn Orbs: Orchestrating Agents at Scale
00:34:42 - How Dario Triages 60 Bug Reports a Day With Agents
00:39:23 - Avoiding Burnout When Agents Remove the Ceiling