Your backlog’s night shift: AI that turns tickets into PRs

What it does

Pilot is a Go-based orchestrator that sits between your issue tracker and your repository. It polls GitHub, Linear, Jira, or Asana for labeled tickets, delegates planning and implementation to Claude Code, runs tests and linting, and opens a pull request. You review and merge; it can even wait for the merge before starting the next ticket to avoid branch collisions.

The interesting bit

The project treats autonomy as a dial, not a switch. Its dev, stage, and prod autopilot modes decide whether to skip CI, auto-merge after green checks, or demand human approval for every step. It also routes trivial tasks to Haiku and complex ones to Opus 4.6, and runs a self-review pass before it ever bothers you with a PR.

Key highlights

• Label-driven workflow: tag an issue pilot and it claims the ticket, branches, codes, and opens a PR.
• Built-in cost controls with hard budget limits and persistent SQLite metrics for token spend.
• Telegram bot integration for chat, voice, image analysis, and on-demand research or planning.
• Cross-project memory and parallel Haiku-powered research subagents for codebase exploration.
• Desktop app and terminal dashboard with sparkline metrics, queue depth, and hot-upgrade support.

Caveats

• The README still carries a TODO for a demo video and ends with a truncated config sample (default_branch:), so the polish is not quite there yet.
• It is fundamentally a sophisticated orchestration layer around Claude Code CLI; you must bring your own API keys and the separate CLI binary.
• Licensed under BSL 1.1, which is source-available but not OSI-open-source, so check the terms before baking it into your commercial stack.

Verdict

Teams already paying for Claude Code and managing a backlog of discrete tickets will get the most mileage; if you need a fully self-contained coding model or strict OSI-approved open source, this is not your tool.