GitHub App and projects
Create your organization's own GitHub App, sync repositories into projects, create repositories, and work with projects that have several repositories.
Create the app
Settings → GitHub → Create GitHub App (administrators) creates the organization's own app with GitHub's
app-manifest flow: you confirm on GitHub, and GitHub hands the credentials back to your control plane, where they
are stored encrypted with ENCRYPTION_KEY.
- Owner: a GitHub organization, or empty for your personal account.
- Installable on any account (default), but installations are accepted only when started from Install on an account on that page (a single-use link).
- Permissions: repository contents, pull requests and issues (write), metadata (read), administration (write, to create repositories in organizations).
GITHUB_URLandGITHUB_API_URLpoint it at GitHub Enterprise Server.
Sync
Every repository an installation can see becomes a project (unless already in one); archived repositories are not
imported, and repositories the app can no longer see are marked no access, never removed. Syncing happens through
webhooks when PUBLIC_URL is reachable from GitHub, and by polling every ten minutes; Sync now syncs at once.
New repositories
New project → New GitHub repository creates a repository with a first commit and a project for it. In a personal account the app must be installed there and you connect your GitHub account once. Workers with a projects folder can clone it right away.
Projects with several repositories
Add repositories on the project page (Repositories). One is primary; tasks see all of them. Only workers with a checkout of every repository and an agent that can work in several directories (Claude Code) run such tasks.
Verification status
The app flow, sync, webhooks and scoped tokens are tested against a local fake of GitHub's web and REST API, not yet against github.com.