When should you use it?
- You want many agents working at once without stepping on each other
- Agents must never touch a developer's personal credentials
- Your team already uses remote dev environments
Not for: Solo developers without cloud infrastructure; Repos where nobody reviews agent pull requests
What do you need, and what do you get?
You need
- Standard cloud developer machines
- An agent harness you can customize
- An internal tool catalog the agent can draw from
You get
- One clean environment per agent task
- Pull requests ready for human review
- Fewer CI failures thanks to earlier checks
How does it work, step by step?
- Reuse your dev environmentRun agents on the same replaceable cloud boxes engineers use, so isolation and parallelism come for free.
- Keep a warm poolPre-provision boxes with repos cloned and caches warmed so a run starts in seconds.
- Curate a small toolsetPick only the tools each agent needs from the wider internal catalog, since a narrow set performs better.
- Share guidance across agentsSync rule files so every coding agent in the company reads the same conventions.
- Shift feedback leftRun lint and known CI checks inside the agent loop before anything is pushed.
The prompt
Our own prompt, inspired by Alistair Gray and written to work in Custom agent. Values in lime are placeholders.
You are running unattended on a fresh devbox for task [ticket ID]. Use only these tools: [tool list]. Read the repo's rule files first. Make the smallest change that resolves the ticket, run lint and the relevant tests locally, and fix failures before pushing. Open a pull request with a summary, test evidence and anything you were unsure about. Never use personal credentials or touch production systems.
Inspired by Alistair Gray: Minions: Stripe’s one-shot, end-to-end coding agents—Part 2. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Giving every tool to every agent made results worse, according to the authors.
- Unattended agents still need human review on every pull request.
Our take
The interesting lesson from Stripe is that the work they did for human developers years ago is what made unattended agents safe. If your engineers already use disposable cloud machines, you already have most of the hard part. Narrowing the toolset is worth copying even at small scale: an agent with five relevant tools beats one with fifty it might misuse. Shared rule files and shifting lint feedback earlier, before CI, catch problems while the agent can still fix them cheaply. Start by giving agents one category of chore, such as flaky test fixes or dependency bumps, and measure merge rate and revert rate before widening scope. Keep human review on every pull request at first, and only relax it for the narrowest, best-tested classes of change. Pre-warmed pools matter for latency; cold starts kill the economics of many small agent runs. Never point unattended agents at production credentials. Track how many of their pull requests are reverted within a week as your real quality signal.
Where the time goes back: Isolated, ready-made environments remove setup time and blast-radius worries, so engineers can hand off many small tasks at once.
FAQ
Is the code really unreviewed?
Which agent is underneath?
Source and credit
Inspired by Alistair Gray. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Minions: Stripe’s one-shot, end-to-end coding agents—Part 2
- Creator
- Alistair Gray
- Published on
- stripe.dev
- Original date
- Feb 19, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.