2.4.1-beta.1) — updated automatically on every beta release.Switch to stable →Guides
Updating ak
Check for releases, review changes, update on your channel, and roll back when needed.
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
Stay on the beta channel with an explicit flag:
ak self-update --check --channel beta # is a newer release available?
ak changelog --since-current --channel beta # what changed since my version?
ak self-update --changelog --channel beta # print the verified changes directlyApply
Manual CLI apply requires --yes:
ak self-update --channel beta --yesPackage-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 # ScoopA manager installed elsewhere on the machine is not enough — the resolved
running executable must live inside that manager's prefix for ak to treat it
as managed.
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=beta AK_VERSION=<previous-tag> shak 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 --latestRecord the resulting ak --version and ak doctor --json if you are reporting
an update problem.