Skip to main content
A conductor-shaped orchestrator: one repository, many concurrent workspaces, each from its own base ref and each ending in its own pull request — and an app that never runs git, never talks to a forge directly, and never reconstructs a file. Source: examples/coding-orchestrator in the repository. The index at examples/README.md compares all eight side by side.

Golden journeys

  • Connect a repository and spin up workspaces from chosen base refs
  • Watch and steer a running workspace
  • Ship a pull request, then keep answering review comments on it
  • Share a workspace with a teammate whose writes are attributed to them

Platform surfaces exercised

Projects and branches, Connections and use_connection PermissionAssignments, Sessions, coordinator threads and attribution, capability support.

Before it can run

The example’s README carries the five-minute path. Two prerequisites are not the app’s to satisfy and are stated there rather than assumed:
  • A use_connection PermissionAssignment. A Git Project resolves through its Connection, and the acting Principal must both own it and hold use_connection — see Projects. The example mints the PermissionAssignment when a repository is connected.
  • A repository webhook at the provider, pointing at Checkfu’s signature-verifying Watch ingress and registered by whoever operates the deployment. The example receives no webhook and relays no webhook content: the wake carries identifiers only and re-reads the provider fresh.

From the source

The whole orchestration surface the app is allowed to have — note that nothing here exposes a file, a diff, or a git command:
path=examples/coding-orchestrator/server/src/checkfu-runtime.ts
This block is quoted from the file, not retyped: pnpm agent-docs:check fails if it drifts.

Honest gaps

Recorded in examples/coding-orchestrator/README.md. Counts are deliberately not repeated here — they differ per tree, and examples/README.md carries them with the sha they were measured at.