Internal · four client codebases
Overnightengineering agents
Tickets go in during the day. Pull requests, linted and type-checked, are waiting in the morning. A human merges.
- Client
- Internal · four client codebases
- Kind
- Agentic pipeline · CI
- Year
- 2025–2026
- Status
- Running nightly
- Service
- AI Automation
- Stack
- Claude
- GitHub Actions
- TypeScript
- Supabase
- Next.js
How it works
A voice capture lands a ticket in a queue. Overnight, a planner checks out only the repositories the queued tickets touch, an agent writes the spec with the ticket's priority honoured, implements it in an isolated worktree, runs lint, type-check and tests, and opens a pull request.
An automated code review scores each PR; up to two fix commits are allowed before it is handed to a human. Nothing merges without a person.
Outcomes
- 01
Five tickets in, five PRs out by morning
- 02
17 of 24 agent PRs merged
- 03
Median ticket-to-PR under 15 minutes
Book a call
Tell me what you're trying to ship and what's slow.
You'll get a straight answer: a plan, a build, or “you don't need this.”