Update or uninstall Maia
Update the application safely or remove it while deciding whether to preserve data.
Maia keeps application code separate from user data. Updating the application changes the checkout and dependencies; it does not intentionally replace configuration, sessions, memories, skills, cron state, or audit logs under MAIA_HOME.
Check for updates
maia update --checkUpdate Maia
maia updateThe update command fetches the current code, refreshes dependencies, clears stale bytecode, restarts the gateway service when Maia manages one, and prints the current secure-runtime mode. It does not install or reconfigure operating-system software during an unattended update.
For a higher-safety update, create a backup first:
maia update --backupIf you develop inside the installed checkout, commit or back up your changes before updating. An automatic stash is not a substitute for source control.
Repair an installation
Re-running the official installer detects an existing installation and repairs it in place:
curl -fsSL https://ampliia.com/maia/install.sh | bashIf only governed terminal/code automation is unavailable, use the narrower repair path:
maia secure-runtime status
maia secure-runtime setupSee the per-operating-system secure-runtime guide. Maia remains safe and usable in Restricted mode while that system dependency is unavailable.
Uninstall Maia
| Command | Result |
|---|---|
maia uninstall | Interactive removal; asks whether to preserve Maia data. |
maia uninstall --yes | Removes code, launcher, and service while preserving data. |
maia uninstall --full --yes | Also deletes configuration, keys, sessions, jobs, logs, memories, and skills. |
Back up MAIA_HOME before using --full. A later installation cannot recover deleted credentials, sessions, or governance data.
Verify the result
After an update, run:
maia status
maia doctor
maia secure-runtime statusAfter a keep-data uninstall, confirm that the selected Maia home still exists before removing any remaining backups manually.