Skip to main content
How I AI

How Stripe built “minions”—AI coding agents that ship 1,300 PRs weekly from Slack reactions | Steve Kaliski (Stripe engineer)

41 min episode · 2 min read

Episode

41 min

Read time

2 min

Topics

Remote Work, Investing, Design & UX

AI-Generated Summary

Key Takeaways

  • Slack-triggered agent deployment: Stripe's Minion system lets any employee react to a Slack message with a custom emoji to spin up a cloud-hosted development environment, seed it with the message as a prompt, and have an AI agent attempt full resolution — including writing code, running tests, and opening a pull request — without touching a text editor.
  • Cloud environments unlock parallel agent velocity: Running multiple AI coding agents locally causes machine overload. Stripe routes Minions through hosted cloud dev environments, enabling dozens of isolated agents to run simultaneously. Engineering teams not yet investing in cloud-based development infrastructure are the primary bottleneck preventing meaningful multi-agent parallelism at scale.
  • Developer experience investment directly multiplies agent success rates: Agents fail more often in poorly documented codebases. Stripe's pre-existing internal documentation, CI tooling, and blessed developer workflows give Minions a high one-shot success rate on common tasks like API field additions. Investing in DX under an AI initiative is the practical path to securing engineering roadmap time for infrastructure.
  • CI infrastructure remains non-negotiable regardless of code authorship: At 1,300 agent-generated PRs weekly, Stripe relies on test coverage, synthetic end-to-end simulations, and blue-green deployments to validate agent-written code. Human review time freed from writing shifts toward reviewing. Strong CI pipelines are the mechanism that makes high-volume agent output safe to ship.
  • Machine-to-machine payments enable ephemeral agent commerce: Stripe's Machine Payment Protocol, co-designed with Tempo, lets agents pay third-party APIs per session without pre-existing accounts or subscriptions. In a live demo, Claude spent $5.47 planning a birthday party — paying Browser Base, Parallel AI, and Postal Form for individual micro-sessions — pointing toward a business model built entirely around agent consumers rather than human dashboards.

What It Covers

Stripe engineer Steve Kaliski explains how Stripe built "Minions" — AI coding agents triggered by Slack emoji reactions — that generate 1,300 pull requests weekly with no human involvement beyond code review, and demonstrates a second system where Claude agents transact with real third-party services using machine-to-machine payments.

Key Questions Answered

  • Slack-triggered agent deployment: Stripe's Minion system lets any employee react to a Slack message with a custom emoji to spin up a cloud-hosted development environment, seed it with the message as a prompt, and have an AI agent attempt full resolution — including writing code, running tests, and opening a pull request — without touching a text editor.
  • Cloud environments unlock parallel agent velocity: Running multiple AI coding agents locally causes machine overload. Stripe routes Minions through hosted cloud dev environments, enabling dozens of isolated agents to run simultaneously. Engineering teams not yet investing in cloud-based development infrastructure are the primary bottleneck preventing meaningful multi-agent parallelism at scale.
  • Developer experience investment directly multiplies agent success rates: Agents fail more often in poorly documented codebases. Stripe's pre-existing internal documentation, CI tooling, and blessed developer workflows give Minions a high one-shot success rate on common tasks like API field additions. Investing in DX under an AI initiative is the practical path to securing engineering roadmap time for infrastructure.
  • CI infrastructure remains non-negotiable regardless of code authorship: At 1,300 agent-generated PRs weekly, Stripe relies on test coverage, synthetic end-to-end simulations, and blue-green deployments to validate agent-written code. Human review time freed from writing shifts toward reviewing. Strong CI pipelines are the mechanism that makes high-volume agent output safe to ship.
  • Machine-to-machine payments enable ephemeral agent commerce: Stripe's Machine Payment Protocol, co-designed with Tempo, lets agents pay third-party APIs per session without pre-existing accounts or subscriptions. In a live demo, Claude spent $5.47 planning a birthday party — paying Browser Base, Parallel AI, and Postal Form for individual micro-sessions — pointing toward a business model built entirely around agent consumers rather than human dashboards.

Notable Moment

Kaliski described receiving AI-generated product feedback from multiple Stripe users within 30 seconds — each had used Claude or Codex to both implement Stripe's API and then write the feedback response, meaning Kaliski was effectively receiving communications from agents, not humans, without initially realizing it.

Know someone who'd find this useful?

Episode Transcript

At server landing about 1,300 PRs that have no human assistance besides review per week. A lot of where our work begins is it could be in a Google Doc as we're planning a new feature, or maybe a GR ticket comes in, or we're talking about something in Slack. I can click an emoji, and then the menu will sort of attempt to one shot resolving that prompt using all the tools that are available at Stripe. When you're in larger organizations, there's so much friction that can come between a good idea and getting it into the world. Not only can I have one of these, but I could have many, many of these running in parallel in isolated environments, making isolated changes all at the same time? How are you getting all this code review done? Whether the text has been written by Steve or the text has been written by Steve's robot, you still want that CI environment that's providing confidence that the code that's being changed is safe and that as it rolls out, we're having blue green deployment so you can roll back to. All that is super critical independent of the nature of the authoring of it. No matter how juiced these laptops are, you get three or four work trees in and, like, it starts to sound like an airplane taking off. It's no good. And so I do think on this multithreading agentic engineering work, cloud environments and virtual environments are so important to unlock velocity. Welcome back to How I AI. I'm Claire Vaux, product leader and AI obsessive here on a mission to help you build better with these new tools. Today, we have Steve Kaliski, a software engineer at Stripe, and he's gonna show us how the Stripe team deploys a bunch of pinions to do their engineering work. We'll also watch an agent spend a little bit over $5 to plan a birthday party all in Claude code. Let's get to it. This episode is brought to you by Optimizely. Most marketing teams aren't short on ideas, but what they are short on is time. And that's exactly what Optimizely Opal gives you back. With AI agents that handle real marketing workflows, you know, like creating content and checking compliance, generating experiment variations, personalizing user experiences, analyzing pages for GEO, even tasks like approvals and reporting. It's your AI agent orchestration platform for marketing and digital teams, plugging seamlessly into the tools you already use, handling the boring busywork, and keeping everything on brand. That leaves marketers with more time to do your actual job. See what Opal can automate for your team by signing up for a free enterprise agentic AI workshop with Optimizely. Find out more at optimizely.com/howiai. Attend live, and you'll get a free pair of Ray Ban Meta AI glasses. Steve, I'm so excited to have you on How I AI because I saw the Stripe minions on the timeline. And one, exceptional …

Get the full transcript (8,084 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all How I AI transcripts →

You just read a 3-minute summary of a 38-minute episode.

Get How I AI summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • by Stripe

    Stripe's Machine Payment Protocol, co-designed with Tempo, lets agents pay third-party APIs per session without pre-existing accounts or subscriptions
  • Claude spent $5.47 planning a birthday party — paying Browser Base, Parallel AI, and Postal Form for individual micro-sessions
  • by Stripe

    Stripe engineer Steve Kaliski explains how Stripe built "Minions" — AI coding agents triggered by Slack emoji reactions — that generate 1,300 pull requests weekly with no human involvement beyond code review
  • Claude spent $5.47 planning a birthday party — paying Browser Base, Parallel AI, and Postal Form for individual micro-sessions
  • by Anthropic

    In a live demo, Claude spent $5.47 planning a birthday party — paying Browser Base, Parallel AI, and Postal Form for individual micro-sessions
  • Claude spent $5.47 planning a birthday party — paying Browser Base, Parallel AI, and Postal Form for individual micro-sessions

company

  • Stripe's Machine Payment Protocol, co-designed with Tempo, lets agents pay third-party APIs per session without pre-existing accounts or subscriptions

More from How I AI

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best AI Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Investing & Markets Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into How I AI.

Every Monday, we deliver AI summaries of the latest episodes from How I AI and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime