Stripe's Minions coding agents produce 1,000+ merged pull requests every week

Stripe built homegrown coding agents called Minions. An engineer starts a task, often from Slack, and gets back a tested pull request. Over a thousand merged PRs a week contain no human-written code, though humans review them.

Organization: Stripe
Industry: Payments
When: Feb 2026
Evidence: Company reported
Agents and tools: Minions (internal)Goose

Reported outcome

More than a thousand pull requests merged each week are fully agent-produced and human-reviewed.

1,000+ per week
Merged agent PRs
None
Human-written code in them

Caveats

Stated by the company that uses the agent (blog, earnings call, interview). Not independently audited.

Figures come from Stripe's own engineering blog.
Every PR is human-reviewed. Merged PR counts do not show the size or difficulty of each change.
Some secondary sources quote 1,300+ per week. We use Stripe's own wording.

What the agent does

An engineer describes a task, often in Slack, and walks away. A Minion works in its own environment, runs tests, and opens a pull request. The engineer reviews and merges it.

How it is built

Reports describe a mix of fixed workflow steps and agent loops ("blueprints"). Fixed steps handle the predictable parts, such as setup and test runs. The agent loop handles the code change. Minions reach hundreds of internal tools through an internal MCP server.

What to copy

Make starting a task as easy as sending a chat message.
Use fixed code for the steps that never change. Use the agent only where judgment is needed.
Give agents the same internal tools your engineers use.

Starter prompt

Written by us, not by Stripe.

Task from Slack: "{message}"

1. Restate the task as acceptance criteria (max 5 bullets).
2. Make the change in a new branch.
3. Run the affected tests and the linter. Fix failures you caused.
4. Open a PR with: what changed, why, how you tested it, and anything
   you were unsure about. If the task is ambiguous, ask one question
   instead of guessing.