Quickstart

This quickstart is for the supported v1 path:

ArgoBox
Hermes
OpenClaw
optional Home Assistant integration

The goal is not “turn on every module.” The goal is to get the control plane running and prove one operator workflow end to end.

1. Start ArgoBox

git clone https://github.com/inovinlabs/argobox.git
cd argobox
./scripts/fork-setup.sh
docker compose up -d

fork-setup.sh now creates private/local-config.sh for nonsecret values like SITE_DOMAIN and SITE_URL. Keep secrets in the credential system, not in a plaintext repo-local .env.

Then open:

http://localhost:4321/admin/setup

2. Configure One Real Target

Start with one trusted infrastructure target:

Proxmox
Docker
Unraid
or another supported adapter you actually intend to use

Do not try to wire every possible backend on the first pass.

3. Generate an Agent Key

Create one agent credential for the runtime you are testing first.

Recommended first runtime:

OpenClaw

The key should only be used through the ArgoBox approval and capability model.

4. Connect OpenClaw

Add an MCP server entry that points OpenClaw at ArgoBox.

Example:

{
  "mcpServers": {
    "argobox": {
      "command": "node",
      "args": ["path/to/argobox/integrations/openclaw/mcp-server.js"],
      "env": {
        "ARGOBOX_URL": "http://localhost:4321",
        "ARGOBOX_API_KEY": "abx_your_key_here"
      }
    }
  }
}

5. Keep the First Workflow Boring

The first workflow should prove the control plane, not show off the entire repo.

Recommended proof:

ask for a safe read
ask for a privileged action
confirm it enters the approval queue
approve it
confirm the audit trail records the result

If that loop is not trustworthy, broader framework or autonomy claims do not matter.

6. Add Home Assistant Second

If you want the canonical homelab automation stack, wire Home Assistant after the first operator flow is already working.

Home Assistant should be treated as:

the automation substrate
not a replacement for the ArgoBox control plane

Current Non-Goals

This quickstart does not try to:

activate every module
prove every backend adapter
demonstrate full framework portability
market ArgoBox as a finished everything-platform

The supported outcome is narrower: one repeatable installation, one visible trust boundary, one real operator loop.