AI infrastructure: the harness, the models, the tools, the privilege
One operator, one harness, several model providers, thirty-five tool servers, and agents that act on real systems instead of chatting about them.
Surveyed 15 November 2026 · public page: internal addresses, ports and credentials are deliberately omitted
Why this is worth a look
Most agent projects stop at the prompt and the demo. The hard part is the tool plane: how an agent reaches thirty-five real services without holding thirty-five credentials.
The second hard part is privilege. Here root is a service with two possible proofs, a scope, a rate limit and an audit trail, so an autonomous agent can act on a production-like host without being trusted with it.
The third is cost. Provider routing, a shared tool process and a spend dashboard per model and per key are what make an agent affordable to run every day instead of in a test.
Sources: the harness config (profiles, model routing, 35 tool servers), its session store, the running services on the host, and a tailnet survey. Verified 15 November 2026. Catppuccin Mocha · Lavender accent