Updating & Uninstalling

Anyy can update itself when it was installed by the native resident installer. The updater verifies release checksums, activates the new binary atomically, and preserves the prior active release as a rollback target when space allows.

Check for an Update

Run the read-only check first:

anyy update --check

It reports:

• the current and latest versions;
• the detected install source;
• whether self-update is supported; and
• a read-only disk-space and release-layout preflight for resident installs.

Check before changing a long-running assistant

Use --check before a planned maintenance window. It does not stop the Gateway or change files.

Apply the Update

For a normal resident installation:

anyy update

If the resident Gateway service is running, Anyy stops it, updates the release and service definition, then starts it again and waits for the updated version to become ready. A manually started Gateway is reported but is not converted into a service automatically.

What happens during an update

1. Anyy resolves the selected Profile home and takes an update lock.
2. It detects the install source and available release.
3. It checks temporary and home-directory space.
4. It downloads the platform archive and checksum file.
5. It verifies SHA-256 and validates the archive before extraction.
6. It installs the candidate in a versioned release directory.
7. It runs the candidate's anyy --version health check.
8. It atomically switches the active release and records the previous target.
9. It restores the Gateway service to its prior running or stopped state.

A completed update prints the old and active versions, rollback availability, command status, and Gateway outcome.

Select a Version

Install a specific published version:

anyy update --version v0.1.105

Replace the example with an available release. Without --version, Anyy follows the latest version reported by the configured release source.

Compact Updates

When disk space is tight:

anyy update --compact

Compact mode removes inactive releases first and keeps the active release. Only when required to pass the space check can it remove the previous rollback target.

Compact mode can remove rollback history

Free disk space manually when possible. --compact preserves user data, but it may leave no previous binary to return to.

What an Update Preserves

The release updater changes program releases and command/service entrypoints. It does not remove your Profile data, including:

• config.yaml and credential files;
• state.db, sessions, and memory;
• Skills and MCP configuration;
• workspace files; and
• backups, logs, and caches.

Run a backup before a high-risk infrastructure change if you need an independent recovery copy:

anyy backup create --output /safe/path/anyy-backup.tar.gz

Credentials are excluded unless you deliberately add --include-secrets.

Other Install Sources

anyy update only self-updates a native resident installation. If anyy update --check reports another source, use that source's normal upgrade workflow:

Source	Update with
Homebrew	brew upgrade ... for the installed formula
npm	The package manager and package name used for installation
Docker	Follow Docker Deployment: rebuild the trusted source image, or pull the configured trusted image, then recreate the service
Source checkout	Update the checkout and rebuild using the project's instructions

Follow the exact guidance printed by anyy update --check; do not mix package-manager files with the native release layout.

Custom Release Mirrors

Operators of a compatible trusted mirror can override the release base:

anyy update --base-url https://releases.example.com/anyy

The mirror controls both artifact and checksum

--base-url changes where Anyy obtains the release and its checksum file. It is not an independent integrity authority. Use only a source you control or trust.

Verify After Updating

Run:

anyy --version
anyy status
anyy doctor

Then reopen Dashboard and send a small test message:

anyy dashboard

If a running service could not be restored, the updater reports a non-zero outcome. Inspect it with anyy gateway status, correct the reported problem, and start or restart the service explicitly.

Uninstall Anyy

Interactive uninstall asks which scope you want and requires confirmation:

anyy uninstall

The two modes are:

Mode	Removes	Keeps
--keep-data	Program releases, command entrypoints, and service	Profile configuration and data
--full	Program releases, command entrypoints, service, and all Anyy data in scope	Nothing in the selected Anyy homes

For a non-interactive uninstall, choose the scope explicitly:

anyy uninstall --keep-data --yes
anyy uninstall --full --yes

--yes without --keep-data or --full is rejected.

Full uninstall deletes personal data

anyy uninstall --full removes Anyy configuration, credentials, sessions, memory, Skills, workspace files, and other Profile data in scope. Create and verify a backup first if any of it matters.

Uninstall is supported for the native resident layout. Package-manager, container, or source installations must be removed with the system that installed them.

Troubleshooting

Problem	Fix
Self-update is unavailable	Use the install-source guidance shown by anyy update --check
Another install or update is running	Wait for the operation holding the selected home lock to finish
Preflight reports insufficient space	Free temporary/home space; use --compact only if reduced rollback history is acceptable
Checksum verification fails	Retry from the trusted release source; never bypass verification
The Gateway does not return	Run anyy gateway status, then anyy gateway start or restart after fixing the reported service error
Uninstall refuses the installation	Confirm this is a native resident install and that --home points to its actual home