What it does

Issue-Orchestrator claims eligible GitHub issues, creates an isolated git worktree for each one and routes it to a configured agent type, so several issues can be worked at once. Coding, review, rework and tech lead sessions run through configured agent providers. It treats an agent reporting that it is done as untrusted input. The orchestrator validates the exact commit produced, runs the validation and review gates you define, allows a bounded number of rework rounds and then publishes a pull request for a human to merge. Agents cannot merge. GitHub labels and observed worktree state serve as the record, so crashes can be recovered. A dashboard moves issues through Queued, Running, Blocked, Awaiting Merge and Completed, with a timeline of review cycles, validation results, transcripts and replayable session recordings. The site describes the project as an early beta at version 0.x, with APIs that may change, and says it works best on repos that already have CI, branch protection and clear engineering standards.

Capabilities

Isolated git worktree per issue for concurrent agent work
Validation, review and bounded rework gates before a PR is published
Crash recovery from GitHub labels and worktree state
Dashboard with timelines, transcripts and session replay
MCP server and VS Code integration
Humans keep merge authority

When to use it

Running coding agents on GitHub issues with enforced quality gates
Repos with CI, branch protection and right-sized issues
Teams that want a person to approve every merge