Product setup and sign-in

The Sync web app is the human control surface for onboarding, status, imports, and incidents. It calls the same public v1 API described by this site.

Sign in

Sync uses Gitdown sign-in and Marketplace OAuth with PKCE. The browser sends Sync only a short-lived token intended for the Sync API; it does not send the raw Gitdown sign-in token or a GitHub installation token. Callback parameters are removed from browser history after exchange.

Connect a repository

1. Sign in with Gitdown.
2. Select or install the Gitdown Sync GitHub App for the account that owns the source repository.
3. Choose the GitHub repository to back up.
4. Review its name, default branch, Git object format, and supported limits.
5. Choose a personal or organization Gitdown owner and create the non-public target.
6. Confirm backup-only mode.

Personal targets are Private and organization targets are Internal. The server revalidates the GitHub installation, repository selection, Gitdown owner, target name, and current versions; browser state is never authority.

Monitor a connection

The connection dashboard shows provider and Gitdown repository identity, connection mode and state, recent reconciliation, the next suggested action, ref checkpoints, imports, incidents, and outages.

Import status is opened by its import ID. A cancellable import requires its current version, and cancellation affects only that import generation. For an eligible retained quarantine, a signed-in human can authorize one successor; the failed generation and its evidence remain visible. Agent sessions can observe that state but cannot authorize recovery.

Incident detail loads preserved tips and lifetime attempt history in pages. For an eligible corrupt-checkpoint quarantine, a signed-in human can authorize retirement of that checkpoint and fresh observation of both endpoints; the UI does not ask the human to choose an object ID or winning endpoint. There is no preselected resolution outcome. Before submitting a resolution, the UI requires every preserved tip to be loaded and every omitted tip to have an explicit disposition and reason. Retry and safe resume appear only when the current incident state permits them.

A 409 response is not retried automatically. The UI reloads current state and requires a new decision against the refreshed evidence. The server remains authoritative for every permission and state transition.

Human-only controls

Only a human can enable two-way mode, reauthorize a GitHub installation, or disconnect a connection. Each action requires confirmation and the current resource version. Agents see only the incident actions allowed by their exact repository grant.

Invited testers can open Sync. To integrate a client, start with the API reference.