git 2.40 or later on your PATH. agentx doctor checks this.
Install
Install with Homebrew, with a package or with the install script. Then runagentx doctor to check that this machine is ready.
With Homebrew
On macOS, install the app with its CLI with Homebrew:agentx command on your PATH, both at the same version. Homebrew also installs a recent git.
To install the CLI alone, on macOS or Linux:
agentx-cli takes about a minute. Install one or the other: both provide the agentx command.
Install the app
Download the app from the latest release:
Each package carries the CLI of the same version, and the app runs only that one. The
.deb also puts the agentx command on your PATH, and requires git 2.40 or later. The disk image and the AppImage do not put agentx on your PATH; the install script does.
The Linux packages run on glibc distributions from 2022 on, such as Ubuntu 22.04 and Debian 12. Those two ship a git older than 2.40, so apt refuses the .deb until you install a newer one. On Ubuntu, add the git-core PPA. Debian 12 has no newer package, so upgrade to Debian 13, which ships git 2.47, or build git from source. The AppImage starts with any git, and then reports one older than 2.40 in its startup check. An AppImage needs FUSE 2: if it does not start, install your distribution’s libfuse2 package, or run it with --appimage-extract-and-run.
The release’s checksums.txt lists the SHA-256 checksum of every download.
With the install script
Install the latest release of the CLI with the install script:agentx to ~/.local/bin, without sudo. If ~/.local/bin is not on your PATH, the script tells you how to add it. If another agentx comes first on your PATH, the script warns you.
To install agentx in a cloud agent’s environment, use the setup script in Cloud agents.
To read the script before you run it, download it first:
sh, put them after sh -s --, for example curl -fsSL https://agentx.wtf/install | sh -s -- --version 0.2.0. When you run a downloaded script, put them after its name: sh install.sh --version 0.2.0.
Update
If you installed the CLI with the install script, update with agentx itself:agentx that ran it. See agentx update for checking without installing, nightly builds and installing one version. Running the install command again also updates. If you installed to another directory, pass the same --dir. Leave out --version, or you get the same version again.
If you installed with Homebrew, run brew upgrade agentx for the app with its CLI, or brew upgrade agentx-cli for the CLI alone. For a --HEAD install, run brew upgrade --fetch-HEAD agentx-cli. agentx update refuses an agentx that Homebrew installed, and tells you so.
If you installed an app package, download the newest one from Install the app and install it over the old one. The app has no updater yet, and agentx update refuses the CLI inside it.
A running agentx serve keeps the old version until it restarts. Quit and open the app to run the new version.
Run agentx version to see which version you have.
Try a nightly build
When the code changed and its tests passed, a new nightly build is published, usually at most every 6 hours, such as0.3.0-nightly.20261001.42. Nightlies get fixes and features first, but they are less tested than releases. Only the 14 newest nightlies are kept.
Install the newest nightly of the CLI:
agentx update moves you to the newest nightly, and agentx update --stable takes you back to the latest release. Running the install command again does the same: with --nightly for a newer nightly, without it for the latest release. If GitHub refuses the command because of its rate limit, set GITHUB_TOKEN and run it again.
For a nightly of the app, download its package from the nightly’s page under releases, and install it as in Install the app.
With Homebrew, run brew install --HEAD grundmanise/tap/agentx-cli to build the latest code of the CLI on main.
Build from source
Build the CLI with Go 1.27.1 or later:dev.
On macOS, keep cgo enabled, which is the default. Without it, agentx serve needs one open file for each watched file and can hit the system limit.
To build the app, see the desktop app’s README.
Uninstall
- Homebrew: run
brew uninstall agentxfor the app, orbrew uninstall agentx-clifor the CLI. To remove the app’s own caches and logs as well, runbrew uninstall --zap agentx; this leaves your data. - macOS disk image: move agentx from your Applications folder to the Trash.
- Linux
.deb: runsudo apt remove agentx. - AppImage: delete the file.
- Install script: delete
agentxfrom the directory you installed to,~/.local/binby default.
~/.agentx by default, keeps its settings and the history of your own skills. Your skills stay in the library, ~/.agents/skills by default. If you install agentx again over the same ~/.agentx, it finds all your managed skills again, your own included.