documentation

Install & operate

The documented install path is the CLI action sequence. Every mutating action is idempotent — running it twice changes nothing.

prerequisites

Host requirements

os

Ubuntu 26.04 (amd64)

Official releases only. Earlier releases are not supported — Podman 5.2+ is required and ships from the official 26.04 repositories.

runtime

Podman ≥ 5.2, rootless

With secret inspect --showsecret. uidmap (newuidmap/newgidmap) for subuid/subgid mappings.

system

systemd

The workspace, policy, and proxy services run as systemd units. A passwordless-sudo operator runs the install.

storage

Disk capacity

Silo state, images, and browser profiles live under /var/lib/agentsilo and the rootless storage of the agentsilo user. Free space is checked by host-prerequisites.

install

The action sequence

Install the host package, then run the actions in order. Add --json to any action for machine-readable output.

# 1 — install the packages
sudo dpkg -i agentsilo_<version>_amd64.deb   # host services + agentsilo-install
sudo dpkg -i agentsilo-desktop_<version>_amd64.deb # operator UI

# 2 — the idempotent action sequence
sudo agentsilo-install host-prerequisites  # read-only: os, podman, uidmap, disk
sudo agentsilo-install images              # build browser/pi/codex silo images
sudo agentsilo-install egress --force      # apply egress firewall policy (the only explicit decision)
sudo agentsilo-install verify              # services, token, socket, images
One deliberate human decision: enabling egress. egress without --force only reports current firewall state.
state

Installation states

The system tracks what it has actually done, so you always know where an install stands:

StateMeaning
InstalledFiles, units, and documentation are present.
ConfiguredIdentities, state directories, policy/proxy services, and token are ready.
Image-readySelected container images are available locally.
VerifiedHealth and acceptance checks passed.
Needs attentionA prerequisite or validation failed — check the --json output of the failed action.
lifecycle

Upgrades, rollback, uninstall

// upgrade

Upgrade

Active silos are stopped before binaries or units migrate. /etc/agentsilo configuration and /var/lib/agentsilo state are preserved; schemas migrate atomically; running silos reconcile as stopped. Installed version is recorded in /var/lib/agentsilo/install-state.json.

// rollback

Rollback

Keep the previous verified .deb. Reinstall it with dpkg -i; state preserved by upgrades is compatible, and silos reconcile back to stopped.

// remove

Remove / purge

Ordinary removal retains configuration and state — silos, policy state, and secrets are never destroyed automatically. Purge is explicit: sudo agentsilo-install purge --force.

// windows

Windows desktop

The NSIS installer installs the operator shell only. Silos run on your Ubuntu host; the client reaches the local services through their narrow interfaces.

Before operating at scale — review the security notes. AgentSilo is not a credential vault and not a VM boundary; know the residual risks before pointing real agents at it.