Skip to the content

Install on Linux

Install AgentGarm on Debian, Ubuntu, Fedora or RHEL, then start its services.

Install the package

Download the .deb or .rpm for your architecture from the download page, verify it, and install it:

sudo apt install ./agentgarm_X.Y.Z-1_amd64.deb
sudo dnf install ./agentgarm-X.Y.Z-1.x86_64.rpm

Both depend on git, and recommend libfido2's tools for security-key approvals preview.

Start the services

The package installs the programs and runs no script. An administrator then installs the daemon, the per-user session service and each agent's managed hooks, which nothing installs by itself: without them no command or file rule is decided. agentgarm doctor checks the result:

sudo agentgarmd install
sudo agentgarmd install --session
sudo agentgarmd hooks install claude-code   # once per agent: codex, cursor, …
agentgarm doctor

The session service is installed for every user and starts at each user's next login. To start it now, run this as yourself before agentgarm doctor:

systemctl --user daemon-reload
systemctl --user start agentgarm-session

Each agent's guide covers its hooks: Claude Code, Codex, other agents.

Then follow the quick start, and once it runs:

Upgrade

Verify the new release's package, install it over the old one, then restart the services: no package runs a script, so the old daemon keeps running until you do, and agentgarm status and agentgarm doctor say it needs a restart. When a release's notes say its service unit changed, run sudo agentgarmd install before the restart. Your policies, the audit log and the store carry over as they are; the restarted daemon points the agents' hooks at the new release by itself, and agentgarmd hooks status says stale for one it has not reached yet.

sudo apt install ./agentgarm_X.Y.Z-1_amd64.deb   # or: sudo dnf install ./agentgarm-X.Y.Z-1.x86_64.rpm
sudo systemctl restart agentgarmd
systemctl --user restart agentgarm-session   # as each user
agentgarm doctor

Remove it

Uninstall the daemon first: it removes every agent hook and MCP configuration it installed, restoring what was there before, then its service. If one cannot be removed, the service is kept and the command fails and lists it, because a fail-closed hook left behind would deny every call of its agent; fix what it lists and run it again (--force removes the service anyway, and still fails). Then the session service, then the package. A session already running keeps running until its user logs out.

sudo agentgarmd uninstall
sudo agentgarmd uninstall --session
sudo apt remove agentgarm   # or: sudo dnf remove agentgarm

Your policies, the audit log and the store stay in /var/lib/agentgarm and /etc/agentgarm, so a later install picks them up. Export the audit log first if you need it (the audit log guide), then delete that directory to remove them too. A presence key is not removed: on a Mac its handle stays in each user's ~/Library/Application Support/AgentGarm/presence (the key itself never leaves the Secure Enclave), and on Linux a security key keeps its credential.