Skip to content

Backup and Profile Data

Treat the entire active Pioneer home as one profile. The current product does not provide a live snapshot coordinator across its SQLite databases and file stores.

Create a consistent file backup

  1. Open Machine and record the active Pioneer home and profile ID.
  2. Stop the Pioneer backend cleanly. Stop in-flight runs and resolve or abandon live approvals first.

  3. Copy the whole home to a new timestamped directory:

    $PioneerHome = Join-Path $env:USERPROFILE "PioneerAI"
$BackupParent = Join-Path $env:USERPROFILE "PioneerBackups"
$BackupPath = Join-Path $BackupParent ("PioneerAI-" + (Get-Date -Format "yyyyMMdd-HHmmss"))
New-Item -ItemType Directory -Path $BackupParent -Force | Out-Null
Copy-Item -LiteralPath $PioneerHome -Destination $BackupPath -Recurse
$BackupPath

  4. Start the backend again and re-verify the profile.

Do not treat a copied config.json alone as a complete profile backup. Installed Ollama models are outside Pioneer home and require their own provider backup strategy.

Restore safely

Stop the backend before using a copied profile. The safest verification path is to start Pioneer with PIONEER_HOME pointing at the restored copy, then inspect Machine, Sessions, Memory, Saved Flows, and Executions. Do not overwrite an active normal profile merely to test a backup.