Install with an agent
Point any CLI coding agent at this and it can do the install:
https://www.hexaeight.com/llms-install.txtThat file is the complete install procedure, written to be followed rather than read — every command is exact, the folder layout is fixed, and nothing needs fetching from anywhere else. Paste this to your agent:
Install HexaEight on this machine by following https://www.hexaeight.com/llms-install.txt — read it first, tell me which OS section applies, and ask me for the licence code and the provider API key before you start.
One step stays yours
Section titled “One step stays yours”Activating the licence. hexaeight-activate newtoken asks for a password that should not pass
through an agent, and needs a QR code approved in the Authenticator
on your phone. The agent creates the folder, hands you the command and waits. Everything else is its
work — and the cards tell it so, explicitly.
It will also ask you for a provider API key, and show you the model list so you choose the model.
Before it installs anything, it should ask
Section titled “Before it installs anything, it should ask”Identity lives on your phone, so the first card is questions, not commands: is the Authenticator installed, is your email vault set up, do you have a licence code, and what should the agent be called — a generated name, or a host on your own domain. An agent that starts running commands before asking those has skipped the first card.
The folders it will use
Section titled “The folders it will use”| folder | what it is |
|---|---|
~/hbia-agent | the licence folder — newtoken runs here, nothing is installed here |
~/heia-agent | the installed agent |
~/heia-router | the router |
~/heia-runner | a runner agent, optional |
That is the preferred layout, and what an agent will use unless you say otherwise. The
single-folder convention in INSTALL.md — the agent living inside ~/hbia-agent
alongside the licence — works just as well, so if you already have it, keep it. Either way the
licence files are hardlinked into each component folder, never copied.
What the file contains
Section titled “What the file contains”Each card is one job: what it is for, the exact commands, the rules to apply exactly, what must never be done, and what done means. Cards are marked by OS, so an agent reads only the ones for the machine in front of it.
| OS | cards | |
|---|---|---|
| Any OS | 9 | install-authenticator-first, install-choose-resource-name, install-licence-human, install-router, install-agent, install-workspace, install-autostart, install-runner, upgrade-components |
| Linux | 1 | install-preflight-linux |
| macOS | 2 | install-preflight-macos, install-agent-macos-hardening |
| Windows (WSL) | 1 | install-preflight-windows-wsl |
Three failures that look like success
Section titled “Three failures that look like success”Every component running, every check green, and no turn ever answers. The cards cover all three:
| macOS binary not re-signed after download | Killed: 9 — reads as a crash, is a signature |
| macOS jail masks the folder, not the files | every engine dies with EPERM |
engines sealed to an -oai- route | 400 modelCode: does not exist — reads as a bad model id |
The longer human version
Section titled “The longer human version”Installing is the same procedure as a page to read. The full source is INSTALL.md, which is itself written for an AI agent.
For the rest of the documentation as machine-readable text, see For AI agents.