Stripe
Minions unattended coding agents
Stripe reported over 1,000 weekly merged pull requests produced entirely by Minions agents
Problem
Engineering attention limited how many tasks Stripe could complete. Coding agents also needed access to the company's unusual codebase and internal development tools.
Approach
Stripe built Minions to run coding tasks without interaction between initiation and pull request preparation. Engineers commonly started tasks from Slack, with linked context available to the agent. Minions used internal tools and automated checks, while engineers reviewed the resulting code before merging.
Results
Takeaway
Unattended implementation still ended in human review. The reported merge volume did not establish net engineering time saved.
Categories
- Size
- Large enterprise
- Industry
- Finance and insurance
- Business function
- IT and R&D
- Innovation type
- Process innovation
- AI technology
- Generative AIAI agents
- Adoption
- Built in-house
- Evidence
- Company's own claim
Sources
Source summaries
Stripe described its internal unattended coding agents and their integration with development infrastructure. It reported weekly merge volume for agent-written code that received human review.
Full details are in the original sources.