One-shot coding agents started from team chat
Engineers kick off an agent from a Slack thread; it works in a dev environment and returns a PR for human review.
The use case
Stripe described Minions, internal agents that engineers start from Slack or other tools with a short request. Each run gets its own pre-built development environment, uses internal tools and docs through connectors, runs linters and tests, and ends with a pull request. Stripe says many such PRs merge each week, and every one is reviewed by an engineer. The design point is that the agent finishes in one go rather than waiting on chat back-and-forth. Teams copying the idea still need fast sandboxes, a good test suite, and clear rules that humans review and merge.
Example workflow
- Engineer describes the task in a chat thread
- Agent spins up an isolated dev environment
- Agent edits code, runs checks and writes a summary
- Agent opens a pull request and posts the link
- Engineer reviews and merges or closes
Tools
- Slack
- Goose
- GitHub
- CI
Risks and guardrails
- Agents with internal tool access need strict permissions
- Volume of PRs can overwhelm reviewers
- Chat requests can be vague; require clear task wording
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Stripe Dot Dev blog: Minions: stripe.dev/blog/minions-stripes-one-shot-end-to-end-coding-agents
- Slack MCP server (official page): docs.slack.dev/ai/slack-mcp-server (checked 2026-11-09)
- GitHub MCP server (official page): github.com/github/github-mcp-server (checked 2026-11-09)