Updating ak

ak updates itself from the signed release channel. Every update verifies the release metadata and the target artifact before replacing the running binary.

Check first

Pass --channel stable explicitly — an empty channel defaults to beta:

ak self-update --check --channel stable           # is a newer release available?
ak changelog --since-current --channel stable     # what changed since my version?
ak self-update --changelog --channel stable       # print the verified changes directly

Apply

Manual CLI apply requires --yes:

ak self-update --channel stable --yes

Package-manager installs

If ak proves the running binary belongs to a package manager (Homebrew, Scoop), both check and apply report a managed install and print the manager-native command instead of replacing files:

brew upgrade ak      # Homebrew
scoop update ak      # Scoop

Roll back

To return to a previous binary release, reinstall that version. Binary self-update does not create an ak backups record:

curl -fsSL https://agentkit.best/install.sh | AK_CHANNEL=stable AK_VERSION=<previous-tag> sh

ak backups restore rolls back project/lifecycle state snapshots (for example after ak update or kit uninstall), not the installed binary:

ak backups list
ak backups restore --latest

Record the resulting ak --version and ak doctor --json if you are reporting an update problem.