Managing Packs¶
By the end of this page, you'll know how to browse, install, upgrade, and remove capability packs on your KruxOS appliance.
Packs extend KruxOS with new typed capabilities — weather lookups, RSS feeds, custom integrations, and more. Pack code runs inside the same per-agent sandbox as built-in capabilities, so installing a pack doesn't weaken isolation.
flowchart LR
REG[Pack registry<br/>docs.kruxos.com/packs] -->|install| APP[KruxOS appliance]
UP[Upload .tar.gz] -->|install| APP
APP -->|hot-reload| GW[Gateway<br/>new capabilities visible]
GW --> AGT[Agents + policy editor]
Browse installed packs¶
Open Packs in the dashboard sidebar. The page shows:
- Registry tab — browse packs from the community registry with search and one-click install.
- Installed tab — packs currently on your appliance with version, capability count, and remove action.
Each installed pack's capabilities appear immediately in the policy editor and in tools/list for connected agents — no gateway restart needed.
Install a pack¶
- Open Packs → Registry.
- Search or scroll to find a pack.
- Click Install. KruxOS downloads, verifies, and installs the pack.
- The pack moves to the Installed tab with a success toast.
- Open Packs → Installed.
- Click Upload pack and select a
.tar.gzpack archive. - Or copy the file to
/data/kruxos/uploads/via the Uploads page and paste the path.
Upgrade a pack¶
When a newer version is available in the registry, the Installed tab shows an Upgrade button:
Upgrading replaces the pack's capabilities in place. Agents pick up the new definitions on their next tools/list call.
Remove a pack¶
Removed pack capabilities disappear from the policy editor and from agent tool lists immediately.
Policy and packs¶
Each pack capability has a default policy tier (autonomous, notify, approval_required, or blocked). You can override tiers in:
- System policy — affects all agents
- Per-agent policy — on the agent's Policy tab
- User policy — on the Identities page
Pack capabilities show up in the visual policy editor with a pack badge so you can tell them apart from built-in capabilities.
Build your own pack¶
See the developer docs:
- Pack Quickstart — create a pack in 10 minutes
- Capability Design Guidelines — write AI-efficient capability definitions
- Publishing — share your pack with the community
Troubleshooting¶
| Symptom | Fix |
|---|---|
| Install fails with checksum error | Re-download the pack; verify the tarball isn't corrupted |
| Capability not visible to agent | Check policy — the tier may be blocked; also confirm the pack shows in Installed |
pack search returns nothing |
Confirm outbound network access from the appliance, or install from a local path |
| Upload too large | Use the Uploads page (streams to disk) instead of browser upload for multi-GB archives |
Next steps¶
- Pack Development Quickstart
- Policies — control which pack capabilities agents can use
- File Transfer — get pack archives onto the appliance