Minions: Stripe’s one-shot, end-to-end coding agents—Part 2 | Stripe Dot Dev Blog
- URL: https://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-agents-part-2
- Saved: 2026-04-10
Part 2 focuses on implementation details behind Stripe’s minions.
Highlights:
- Minions produce over 1,300 merged pull requests per week at Stripe
- They run on standardized AWS devboxes rather than developer laptops
- Devboxes are proactively provisioned and warmed so new environments are ready in about 10 seconds
- Stripe forked Block’s goose and adapted it for fully unattended operation
- Because devboxes are quarantined, minions can run with broad permissions without human confirmation prompts
A key abstraction is the blueprint:
- A blueprint is a workflow defined in code that mixes deterministic nodes with agentic nodes
- Deterministic nodes handle required actions like linting or pushing changes
- Agentic nodes handle open-ended subtasks such as implementation or fixing CI failures
- This pattern keeps reliability high while still letting the agent exercise judgment where needed
Context and tools:
- Rule files are scoped by directory or file pattern to avoid wasting context window on global rules
- Stripe standardized around shared rule formats so multiple coding agents can reuse the same guidance
- Stripe built Toolshed, a centralized internal MCP server with nearly 500 tools
- Agents get curated subsets of tools rather than the entire tool universe
- Existing security boundaries around devboxes also constrain what minions can do
Feedback loops:
- Stripe emphasizes shifting feedback left, catching issues before CI when possible
- Pre-push hooks and local deterministic lint loops reduce wasted CI runs and tokens
- Minions typically get only one or two rounds of CI before handing the result back to a human
- Human developer-productivity investments paid dividends for agent productivity too