Configure Oratorio
Open the Board and select Oratorio settings to manage source connections, project routes, Agent execution, and automation.
Providers and projects
Configure GitHub and GitLab credentials on their provider pages. Add each repository or project separately, then map it to the DotCraft workspace that contains the matching checkout. Oratorio does not guess a fallback workspace for source-backed work.
If a saved Workspace is offline or no longer registered in DotCraft, its binding remains visible as unavailable. Rebind it to an open local Workspace or remove the project. Removing a project stops future sync, automation, and dispatch for that project while retaining existing task history.
Provider pages show read, write, and webhook health. Use Sync now for an immediate update or set a schedule for periodic synchronization. Use a full repair only when the source needs a complete reconciliation.
Agent execution and worktrees
The root page controls approval policy, run timeout, managed Worktree location and branch naming, automatic dispatch, review automation, and delivery behavior. Runtime concurrency, retry, stall, and cleanup policies remain Server-managed and are not exposed in Desktop.
Managed worktrees use the repository-local default root:
<repositoryWorkspace>/.craft/oratorio/worktreesManaged branches use oratorio/run/<work-item-key>. Let Oratorio clean up its own worktrees; cleanup observes persisted run ownership rather than deleting directories by age alone.
Saving and secrets
Settings save after a short delay. A field shows its pending or failed state, and a failed save can be retried. If another editor changes the same revision, Desktop reloads the confirmed server configuration instead of presenting an unconfirmed local success.
An unavailable saved Workspace does not block other Settings changes. Oratorio checks Workspace availability again when it reports health or starts a run.
Saved secrets are write-only. The secret editor provides three explicit choices:
- Keep the stored value.
- Replace it with a new value.
- Clear the stored value.
Some runtime settings require an Oratorio Server restart. Settings reports that state after the configuration is saved.
When Desktop is connected to a remote DotCraft Stack, administrative settings are read-only. Board operations, source sync, and task actions remain available.