guide
Update Prime Agent safely: stable, beta, and rollback
Use prime-agent update to move between stable and beta channels, or reinstall from the official installer. Resident workers may need a coordinated restart, and a daemon/client version mismatch can break protocol compatibility. Always back up important sessions before updating a fast-moving 0.x release.
First-party announcement, documentation, release, or installer.
Stable vs beta channels
Keep stable and beta aligned across the CLI, daemon, and resident worker. Mixing channels is the most common way to create a mismatch.
Check current version
prime-agent --version prime-agent daemon --versionUpdate command
prime-agent update
# or reinstall from the official installer and restart the daemonDaemon compatibility
A fast update can invalidate protocol assumptions. If a worker or daemon was started before the update, stop it and start the whole stack again.
Rollback and recovery
Rollback usually means reinstalling the previous stable release and restoring the last good session JSONL files. Treat the update as reversible until you prove otherwise.
Changelog
Use the changelog after every update to confirm whether a user-visible behavior changed or a claim was rechecked.