Carter's Knowledge Base

Stripe

2 min read

Stripe

Overview

Stripe is described here through its internal unattended coding-agent system, Minions. The articles frame Minions as a response to the realities of operating inside a huge, highly constrained codebase with specialized tooling, compliance requirements, and a strong developer-productivity foundation.

Why it matters

  • Demonstrates that unattended coding agents can work even in a highly regulated, large-scale production environment
  • Shows the value of building on top of existing internal developer infrastructure rather than treating agents as a separate system
  • Offers a detailed view of workflow design: deterministic steps, bounded CI loops, curated tools, and standardized environments

Key facts from sources

  • Minions are fully unattended and one-shot oriented
  • Stripe reports more than 1,000 merged pull requests per week in Part 1 and more than 1,300 per week in Part 2
  • Minions start in pre-warmed devboxes that are ready in roughly 10 seconds
  • The system builds on a fork of Block’s goose and uses a custom orchestration abstraction called blueprints
  • Stripe uses scoped rule files plus a centralized MCP tool layer called Toolshed
  • Local deterministic checks and limited CI iterations are core to the reliability strategy

Design stance

Stripe’s articles repeatedly argue that what is good for human developer productivity is often good for agent productivity too. Devboxes, rule files, CI systems, and internal tool catalogs were all originally human-facing investments that later became powerful infrastructure for agents.

Relationships

Graph View

Backlinks