HexaEight Documentation

HexaEight gives you an AI agent that runs on your own machine and has its own identity. You talk to it in a browser. It searches the information you give it, follows the processes you design, works on your servers and talks to other agents securely, under rules you set.

The picture

1. Your agent has an identity. It is installed on your machine and bound to it, under a name on your own domain (agent.yourcompany.com) or a generated one. It publishes itself under that name, so your workspace and other agents can find it, and every message between them is encrypted end to end and proves who sent it. → Identity
2. It all runs on your machine. Your browser talks to your agent. The agent runs the AI runtime, the harness, for every question, and reaches the model only through your router, which holds the provider key. The answer comes back encrypted end to end. → The harness · What gets installed
3. Nothing to wire up. There are no MCP servers, skill files or instruction files to write. The agent reaches information through memories, and it decides which to search for each question. → Memories
4. Memories from your documents. Add files and they are indexed on your machine, on the CPU. The agent searches them and cites what it used.
5. Memories that reach further. An API you already run, documents another agent serves, or another agent itself can all be memories, searched by name and encrypted end to end. Very large collections are split into shards and searched as one. → An API you already run
6. You see every step, and nothing is allowed until you allow it. The workspace shows which memory the agent searched and what came back. Policy applies at every layer: who may sign in, which agents may call it or be called by it, which commands may run. What it allowed, ran and refused is recorded in a sealed audit trail. → Policy · Audit trail
7. Missions instead of prompts. Describe a process in plain words, and it becomes a flowchart of capability cards that make the decisions, with the memories it may search. It runs the same way every time. Test it in Mission Runner, or hand a long job to HexaPilot. → Missions
8. Bring your framework. CrewAI, LangGraph, Pydantic AI and Agno run on the same harness, with the same identity, memories and policy. → Frameworks

Install it

One command, run twice, on Linux (x86_64), Windows (in WSL) or an Apple Silicon Mac:

curl -fsSL https://raw.githubusercontent.com/HexaEightTeam/hbia-agent/main/install.sh | bash

The first run prepares the machine and stops at the licence, the one step only you can do. The second run installs the rest and ends with the address of your workspace. See What gets installed.

You will need the HexaEight Authenticator app on your phone, which holds your identity, and a licence code. See Installing.

Find your way

Use it	The workspace · Memories · Missions
Connect it	An API you already run · Two agents talking to each other · Your own users · Other software calling it · Frameworks
Models	The router · Run your own · Serve models to agents · Use someone else’s router
Security and compliance	Compliance · Audit trail · Compliance reports · Admin settings · HexaEight and OAuth
Run it	Lifecycle · Encrypted stores · Capacity · Troubleshooting
Understand it	Why this exists · Components · Architecture · Dead Drop Encryption · Trust and permission
Look it up	Every command · Every setting · Glossary

What this is not

It is not a framework you have to write your agent in. Keep what you already have, whether that is a Python service, a REST API or an agent framework, and HexaEight puts an identity, memories and a policy boundary around it. Calling an agent is an authenticated request in and an answer out, in any language. Putting your own code behind one is a process the agent runs; see Bring your own engine.