Updates

Update the desktop and Harness core separately, preserving local work and checking recovery scope.

The desktop and Harness core update independently. Save active tasks and repository changes before choosing the corresponding entry point.

Choose an update entry point

Component	Entry point	What to check
Desktop app	Help → Check for updates	Download and restart when prompted; use the official Release’s platform assets
Managed Harness core	Update prompt or Configuration → Core Engine	Choose compatible versions only; no desktop reinstall is needed
Optional plugins	Configuration → Plugins	Check sources, versions, and errors; restart the service when prompted

The desktop checks for managed-core updates. Network failures do not cause it to delete installed cores, but missing components on first installation still need downloading. The recommended core is 0.2.0-rc.2; the minimum accepted version is 0.1.5-rc.1, subject to compatibility rules.

Update safely

1. Save your work

   Wait for commands and file writes to finish, then commit or separately back up important changes. Profile backups do not include workspaces or complete session history.
2. Read release notes

   Check versions, platforms, and compatibility requirements; upstream and plugin updates can change behavior.
3. Apply the update

   Use the corresponding entry point, keep the app and network available, and wait for the restart.
4. Verify recovery

   Check the active profile, core source, models, and plugins, then send a small test task.

Problems after updating

Copy runtime logs first, then try an installed compatible core or a plugin recovery entry point. Avoid repeated resets or deletion of profiles and application data. Check and back up the relevant directories before destructive repairs.

Profile backups cover only the active profile directory, not workspaces or complete session data. See Profiles and cores for profile details.

See Troubleshooting for startup problems or Profiles and cores for version selection.