Aigon Sync keeps a recovery copy of portable Aigon state in a private Git repository (the vault). It snapshots each registered project’s .aigon/ tree (filtered) plus a stripped copy of ~/.aigon/config.json, then pushes to a remote you control.
It is not the only way to back things up — you can always copy repos, zip folders, or rely on host backups. Aigon Sync adds a hosted recovery snapshot for Aigon-specific state, and is entirely optional.
What gets synced
The vault is a normal Git repo you configure once (aigon backup configure <git-url>). On push, Aigon rebuilds content from your machine, commits, and pushes. Typical layout includes:
projects/<name>/— portable subtree from each registered repo’s.aigon/(sessions, locks, and disposable caches are excluded)settings/— sanitized global config plus workflow definition paths
Pull creates a timestamped local recovery archive, then replaces the filtered
managed .aigon/ scope exactly on machines where those repos exist. This removes
stale managed files left by older snapshots while preserving local sessions,
locks, caches, server state, logs, and other excluded runtime files. Global repo
registration, ports, sync settings, and backup remote/schedule remain local.
Files under .aigon/ that are tracked by the project repository remain under
normal Git authority: push omits them, restore planning ignores them, and pull
preserves the currently checked-out versions.
Pushing from a machine that has only some Vault projects refreshes those local project snapshots and preserves snapshots for projects that are not cloned on that machine. Removing a repo locally therefore cannot silently erase its only Vault recovery copy.
After a successful pull, Aigon sets that machine’s backup schedule to off. Verify the restored state before deliberately enabling scheduled pushes again.
CLI
| Command | Purpose |
|---|---|
aigon backup configure <url> | Point the vault at a private HTTPS or SSH remote |
aigon backup push | Snapshot local state and push to the vault |
aigon backup pull --dry-run | Preview per-project additions, changes, and removals without changing project or settings state |
aigon backup pull | Fetch from the vault and restore where repos resolve locally |
aigon backup status | Remote URL, last push/pull, schedule, project counts |
aigon backup schedule <daily|hourly|weekly|off> | Cadence for automated pushes (the server checks hourly) |
aigon vault is an alias for the same engine as aigon backup.
Legacy aigon sync without subcommands is deprecated — it routes to the backup engine with a migration hint; use aigon backup for new workflows.
Vault backup is a recovery snapshot, not a merge engine. For active feature and
research work across clones or machines, use the repository’s git-branch
SpecStore (aigon storage convert --backend=git-branch --remote=origin and
aigon storage sync) so canonical lifecycle events travel with that repository.
Dashboard (Settings → Aigon Sync)
With the dashboard running, open Settings and choose Aigon Sync. You can:
- See vault remote, last push/pull, and schedule
- Change the Git remote URL
- Trigger Sync now (push) without opening a terminal
Prerequisites
gitand network access to your vault remote- Optional:
ghforgh repo createflows during interactive configure - Repos you care about should appear under
aigon server list/ global config repos so they are included in snapshots
Security & hygiene
- Use a private repository you trust — the vault holds workflow state and stripped config, not your application secrets by design, but treat it like sensitive infra.
- Avoid putting
~/.aigonitself inside iCloud/Dropbox-style synced folders; use Git as the transport.
Related topics
- Scheduling features — deferred kickoffs (separate from vault sync; shares portable
.aigon/stateconcepts) - Dashboard — registering repos and running the server
- Getting started — installing Aigon and registering repos