For AI agents

If you are pointing an AI agent at this documentation, give it one of these:

/llms.txt	the index — what each page covers, small enough to paste into a prompt whole
/llms-full.txt	every page concatenated in reading order, for ingesting in one fetch

Both are generated from these pages, so they cannot drift from what you are reading.

What the index carries

Beyond the page list, llms.txt states the facts an integration usually gets wrong: that identity files are machine-bound, that nothing is enforced until the first policy rule exists, that a person appears in policy as sha512(email), that the router’s only config file is upstreams.yaml, and that the start order is router, agent, workspace.

Sections, in reading order

• Start here — what this is, and the shortest path, POINT AN AGENT AT THIS TO INSTALL — the whole procedure as cards, per OS, installing, by hand or by agent, with the per-OS differences…
• Extending an agent — give it documents to search (memories), put an HTTP service you already run behind it, put your OWN code behind it: a process, declared argv in, JSON out…
• Model access — run your own router; write its rules, forward to someone else’s router, keeping your user list private…
• How it works — why the existing stack cannot do this, the parts, one at a time, how they fit together…
• Operating it — who may do what, start, stop, upgrade, revoke, measured cost per turn, and sizing…