Skip to documentation

Getting started

Connect GitHub

Create a workspace control loop around a repository and GitHub Project.

Sign in with GitHub

Sign in from the Orchestrator landing page. The first successful sign-in creates or selects a workspace. GitHub OAuth remains the hosted integration used to read repositories and update the configured work ledger.

Connect a repository

Workspace owners and admins can choose an accessible GitHub repository, its default branch, and the GitHub Project that Orchestrator should coordinate.

  1. Choose the repository

    Select the repository from the repositories visible to the signed-in GitHub account.

  2. Create or select the Project

    Use the Orchestrator project template or select the matching repository Project.

  3. Review defaults

    Confirm the branch, polling behavior, repository capacity, and initial agent settings.

Select a repository, confirm its Project, and review the local-runner boundary.
Read transcript

The demo opens Add repository, selects a GitHub repository, confirms the Project configuration, reviews the runner notice, and finishes on the repository overview.

Use GitHub as the work ledger

The configured Project tracks Backlog, Ready, In progress, and In review work. Code Agent claims eligible Ready issues, while Repository Review parks new audit findings in Backlog for human prioritization.

Frequently asked questions

Can I connect more than one repository?

Yes. A workspace can coordinate multiple repositories through the same workspace runner.

Who can connect a repository?

Workspace owners and admins can manage repository connections. Members can view permitted workspace activity.

Can Orchestrator create the GitHub Project?

Yes. The onboarding flow can create the Project from the configured Orchestrator template.

What happens if GitHub access changes?

Repository reads or mutations can fail until the signed-in account and workspace regain the required access. Runs surface the failure rather than silently completing.