From the source

How it works
- The original account describes isolated developer environments and repository rules. These require infrastructure and permissions, not just a coding command-line tool.
- Blueprints combine fixed automated checks with model-driven implementation and repair. Toolshed supplies approved tools within Stripe's internal controls.
- Stripe reports more than 1,300 merged pull requests each week containing agent-produced code, with human review.
- Task complexity, failed attempts, review effort, costs and defect comparisons are not disclosed. Human-reviewed does not mean free of human work.
Results
Stripe's Minions Part 2 reports more than 1,300 merged pull requests each week. Unattended coding agents produced all the code in these requests, and humans reviewed it. This is a throughput count. It does not establish a percentage productivity gain, cost reduction or defect-rate improvement. The documented architecture uses isolated developer environments, scoped rule files and a central tool server. It combines fixed automated checks with model-driven implementation. This is an internal architecture pattern, not a public ready-to-run system.
Workflow guide
Select a narrowly defined issue from an approved Slack, command-line or web source. Record its linked context and acceptance criteria.
Prepare an isolated developer environment. Exclude privileged personal workspaces, production secrets and unrelated task files.
Provide applicable repository rules and approved tools. Restrict filesystem and network permissions to the task.
Ask the agent for an implementation plan. Authorize local code changes only after a person accepts the scope.
Run relevant tests and automated checks. Prepare a pull request for human review without bypassing repository security gates.
Compare a fixed issue sample with the previous process. Record failed attempts, task time, correction effort, defects, fees and review time.