← All implementations

Stripe · Background agent

Minions

Homegrown one-shot coding agents that read work context, locate the right repo/workspace, implement a change end-to-end, and produce a PR for human review.

1 Supports3 Contextualizes4 Contextualizes5 Contextualizes6 Contextualizes7 Contextualizes

Approach type
Background agent
Work
Coding, Code review
Human involvement
Drafts reviewed
Invocation
Background, Event driven, Interactive
Interfaces
Slack, Github, Cli, Web, Internal ui
Deployment stage
Scaled
Evidence strength
Detailed primary
Entry reviewed

How it works

The workflow the sources report for this implementation.

Where people stay involved

  • work context → merge-ready pull requestWork product review · Level 3

Level 3 for work context → merge-ready pull request; human attention boundary: work-product-review.

1

Observation date
2026-02-20

Implementation details

Sandbox

Pre-warmed AWS EC2 devboxes in the QA environment, isolated from real user data, production services, and arbitrary network egress

2

Harness

Fork of Block's goose, orchestrated by code-defined blueprints that interleave agent loops with deterministic lint, git, and CI steps

2

Model

Not specified

1

Interfaces

slack, github, cli, web, internal-ui

1

Tool access

Curated subsets of Toolshed MCP tools for internal documentation, tickets, build status, and code intelligence; security controls constrain destructive actions

2

Knowledge

Repository-scoped rule files shared with human-operated coding agents, plus internal context fetched through MCP

2

Credentials

Full permissions inside quarantined devboxes; MCP security controls limit destructive actions, and production pull requests require human review

2

Reported results and limitations

The catalog records what the sources report, with the scope and the denominator of every figure. A qualification below limits the figure it sits under.

Reported metrics

Lessons and interpretation

One-shot end-to-end coding agents work at scale when humans retain review/approval

1

Sources and research details

Citations link to the original publisher. Each source also keeps a preserved copy in the repository, so a changed or removed page stays checkable.

  1. Minions: Stripe's one-shot end-to-end coding agentshttps://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-agentsEngineering blog · First party · Last source verification: 2026-08-31
  2. Minions - Part Twohttps://stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-agents-part-2Engineering blog · First party · Last source verification: 2026-08-31
  3. Hacker News discussion of Minions part twohttps://news.ycombinator.com/item?id=47086557Hn thread · Community · Last source verification: 2026-08-31
  4. Hacker News comment asking for examples and review evidencehttps://news.ycombinator.com/item?id=47086907Hn comment · Community · Last source verification: 2026-08-31
  5. Hacker News comment questioning the level of technical detailhttps://news.ycombinator.com/item?id=47086953Hn comment · Community · Last source verification: 2026-08-31
  6. Hacker News comment asking about shipped and maintained outputhttps://news.ycombinator.com/item?id=47087114Hn comment · Community · Last source verification: 2026-08-31
  7. Hacker News comment questioning the value of pull request countshttps://news.ycombinator.com/item?id=47111453Hn comment · Community · Last source verification: 2026-08-31
Research details for every claim on this page
  1. Summary
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  2. Headline claim
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    Stripe reports merged PR volume without an independent count or measurement window; Part 2 is explicitly later than Part 1.
    Reported by
    Stripe
    Scope
    Weekly merged PRs completely produced by Minions; Part 2 report, up from Part 1
    Denominator
    Not reported
    Method
    Not reported
    Observation date
    Not reported
  3. Sandbox
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  4. Harness
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  5. Model
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  6. Interfaces
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  7. Tool access
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  8. Knowledge
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  9. Credentials
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  10. Supporting component
    Statement type
    Fact
    Provenance
    Reported
    Confidence
    High
    Confidence reason
    A linked first-party source states the claim.
  11. Key observation
    Statement type
    Metric
    Provenance
    Reported
    Confidence
    Medium
    Confidence reason
    Stripe reports merged PR volume without an independent count or measurement window; no calendar metric date appears in the capture.
    Reported by
    Stripe
    Scope
    Weekly merged PRs completely produced by Minions; earlier Part 1 report
    Denominator
    Not reported
    Method
    Not reported
    Observation date
    Not reported
  12. Lesson
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    Medium
    Confidence reason
    The catalog derives this observation from the linked sources.
  13. Lesson
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    Medium
    Confidence reason
    The catalog derives this observation from the linked sources.
  14. Operating model assessment
    Statement type
    Inference
    Provenance
    Catalog judgment
    Confidence
    High
    Confidence reason
    The source explicitly states that humans review and approve production pull requests.
    Observation date
    2026-02-20