Skip to documentation

Overview

Orchestrator documentation

Plan, run, and review AI engineering work through GitHub while execution stays in your environment.

One control plane for the engineering loop

Orchestrator coordinates AI engineering agents across GitHub repositories. GitHub remains the work ledger while the hosted website manages repository configuration, schedules, jobs, run history, and the decisions that require human review.

A local CLI runner performs the work. It connects outbound to the hosted control plane, starts isolated Kubernetes workloads, and returns events and verified GitHub artifacts.

  • Issue Planner turns rough intent into reviewable GitHub work.
  • Code Agent implements eligible project issues and opens pull requests.
  • PR Review evaluates eligible pull requests and publishes review evidence.
  • Repository Review creates deduplicated maintenance work from scheduled audits.
  • Custom agents combine supported triggers with verified GitHub outcomes.

Control stays hosted. Execution stays local.

The website stores configuration and coordinates work. Source checkouts, provider credentials, and agent execution remain in your runner environment.

  1. GitHub signals work

    A project issue, pull request, schedule, or planning brief becomes eligible.

  2. The control plane queues it

    Orchestrator applies repository settings, capacity, and the selected agent contract.

  3. The runner executes it

    The CLI claims the job and starts a short-lived, isolated workload.

  4. Evidence returns

    Events, usage, status, and the verified GitHub outcome appear in the website.

Start with one repository

Connect a GitHub repository and Project, register the workspace runner, configure at least one provider, and enable the work loop. The getting-started guides cover the complete path.

Frequently asked questions

Is Orchestrator a hosted coding agent?

No. The hosted website coordinates work, but repository checkouts and model execution stay in the local runner environment.

Does Orchestrator replace GitHub Projects?

No. It uses GitHub issues, pull requests, reviews, and Projects as the visible work ledger.

How many runners does a workspace need?

The current product uses one registered runner per workspace. That runner serves every enabled repository in the workspace.

Which model providers are supported?

The current runner supports OpenAI, Anthropic, and OpenRouter through authenticated live model catalogs.