An engineer sends a request through Slack or an internal app. The agent prepares a pull request for human review.
Start a run from Slack or an internal app
An engineer tags the Slack app from the thread discussing a change, or starts a minion from the CLI, the web interface, or an integrated internal tool such as the flaky-test ticketing UI[Source 1]
Hydrate context before the run
Relevant MCP tools run deterministically over likely-looking links before the run starts, and rule files scoped to subdirectories attach as the agent traverses the filesystem[Source 1, Source 2]
Implement the task in a prewarmed devbox
The blueprint's agent nodes implement the change in an isolated devbox, interleaved with deterministic lint, git, and push nodes[Source 2]
Open the pull request for human review
The minion prepares a pull request following Stripe's PR template; the engineer opens it and requests review, or sends further instructions that push updated code[Source 1]
Where people stay involved
People review, approve, or guide the agent’s work here.
Reported: Runs are unattended; the engineer opens the prepared pull request for review or returns it with further instructions.
Supervision level
Work-product review
A person reviews the draft or implementation.
3/5Level 3 of 5
coding task → pull request handed to an engineer for review[Source 1]
Fork of Block's goose, orchestrated by code-defined blueprints that interleave agent loops with deterministic lint, git, and CI steps[Source 2]
Sandbox
Pre-warmed AWS EC2 devboxes in the QA environment, isolated from real user data, production services, and arbitrary network egress[Source 2]
Tool access
Curated subsets of Toolshed MCP tools for internal documentation, tickets, build status, and code intelligence; security controls constrain destructive actions[Source 2]
Knowledge
Repository-scoped rule files shared with human-operated coding agents, plus internal context fetched through MCP[Source 2]
Context management
Subdirectory-scoped rule files attach as the agent traverses the filesystem, relevant MCP tools run over links before the run starts, and blueprint nodes can constrain tools or simplify each subagent's context[Source 1, Source 2]
Credentials
Full permissions inside quarantined devboxes; MCP security controls limit destructive actions, and production pull requests require human review[Source 2]
Interfaces
Slack, CLI, web, and internal tools are named; the pull-request host is implied by the branch-and-PR flow but never named in the captures.
Prepares a branch for human review and returns after a limited number of CI repair attempts[Source 1, Source 2]
Validation and failure handling
Repair CI failures within a bounded loop
After a push, CI applies autofixes and sends unfixable failures back once for local repair; after at most two CI rounds the branch returns to its human operator[Source 1, Source 2]
Reported observations
These results come from the sources. Notes below each result explain what it covers and any reported limits.
Headline claim
Over 1,300 completely minion-produced PRs merged per week in Part 2, with human review and no human-written code[Source 2]
Reported by
Stripe
Scope
Weekly merged PRs completely produced by Minions; Part 2 report, up from Part 1
The source does not report the denominator of this figure.
About this result
Category
Adoption output
Evidence type
Reported measurement
What it covers
Weekly merged minion-produced PRs at Stripe, human-reviewed, per the Part 2 report
Key observation
Over 1,000 completely minion-produced PRs merged per week in Part 1, with human review and no human-written code[Source 1]
Reported by
Stripe
Scope
Weekly merged PRs completely produced by Minions; earlier Part 1 report
The source does not report the denominator of this figure.
About this result
Category
Adoption output
Evidence type
Reported measurement
What it covers
Weekly merged minion-produced PRs at Stripe, per the earlier Part 1 report
Lessons
Stripe's Minions produce changes unattended, then return them for engineer review; failed runs can receive further instructions.[Source 1]
Stripe starts Minions in prewarmed devboxes with recent copies of its main repositories and prepared development services.[Source 2]
Reported: The one-shot characterization and the bounded CI repair loop sit under mechanism and validation; the four steps above are the run in reading order.
human involvement
Reported: Runs are unattended; the engineer opens the prepared pull request for review or returns it with further instructions.
implementation
Reported
validation
Reported: A deterministic local lint node and one or two CI rounds with autofixes check the work before the branch returns to its human operator.
Part 1 distinguishes unattended implementation from human PR review and explicitly describes another instruction cycle when the result is insufficient.
