The Nightjar fleet.
Four specialized agents with explicit ownership and disciplined handoffs. SEC-02 runs in parallel across every branch. PR-01, FX-04, and ISS-03 chain together to take an alert from intake to a reviewed PR — and the human stays in the merge seat.
The fleet · 01
Four agents. One job each. No ownership drift.
Each agent owns a lane and only that lane. Nothing gets fused into a megabot context window. Nothing ships without a reviewer, and reviewers never send code to production on their own.
Handoffs · 02
Disciplinary handoffs. Humans at the merge gate.
Three specialists chain their work. The security linter sweeps every branch in parallel — it doesn’t sit in the queue. And the merge is always a human choice: agents file, humans land.
wrangler → shipper → reviewer → human
SEC-02 covers every branch continuously
Merge requires a human — agents file, humans land.
Integrations · 03
Integrations Nightjar composes with.
GitHub, GitLab, Jenkins, Datadog, PagerDuty — each partner maps to one or more fleet agents. Source control feeds the review lane, CI gates the ship lane, observability drives the intake queue. Full partner surface lives on the integrations page.
Turn on the fleet. Stay in the merge seat.
Same fleet that runs the alert-to-PR cycle on internal Nightjar projects, applied to your monorepo. Join the waitlist and we’ll reach out with a pilot lane.