Welcome to ArgoBox

ArgoBox is a private AI control plane for homelabs.

The current public story is intentionally narrower than the full repository. Instead of treating every package, module, and experiment as equal, ArgoBox is focusing first on one hardened stack:

ArgoBox for approval, audit, and capability gating
Hermes for operator-facing routing and orchestration
OpenClaw for agent execution
Home Assistant for the home automation substrate

If you are evaluating ArgoBox today, evaluate it against that stack first.

What ArgoBox Is

ArgoBox sits between AI agents and infrastructure.

Instead of giving an agent raw shell access to Proxmox, Docker, Unraid, or Home Assistant, ArgoBox enforces:

approval-first mutations
capability-scoped access
audit logging
rate limits
operator-visible routing

The point is not “let AI do anything.” The point is “make useful agent actions possible without blind trust.”

The Canonical V1 Stack

ArgoBox

ArgoBox is the control plane:

approval queue
audit trail
capability gating
operator dashboard
infrastructure adapter surfaces

Hermes

Hermes is the operator-facing routing layer:

accepts requests and operator intent
decides what stays read-only
decides what needs approval
routes work to the right subsystem

OpenClaw

OpenClaw is the agent runtime:

asks for actions through ArgoBox
does not receive implicit raw infrastructure trust
operates inside the approval and audit model

Home Assistant

Home Assistant is the current home automation substrate:

mature ecosystem
strong local-first story
practical homelab wedge
better fit than reinventing home automation from scratch

Audience Order

ArgoBox is not trying to win every audience equally on day one.

Current order:

Homelabbers
Developers
AI operators

That means:

the install path must be boring and repeatable
the OpenClaw trust boundary must survive hostile review
the framework story must come from a hardened core, not from branding alone

What ArgoBox Is Not Promising Yet

ArgoBox is not currently claiming to be:

the universal answer for every self-hosted workflow
a finished framework for all developers
a fully autonomous agent runtime with no human oversight

There are many useful modules and experiments in the repo. They are real, but they are not the current public wedge.

Repository Shape

The repository still contains a broader mix of:

public site surfaces
admin/operator surfaces
publishable packages
internal-only packages
experiments and preserved work

That breadth is real history, but the current direction is narrower: one homelab-first control plane with a clear trust model.