Find your way in
Get startedInstall, configure, load claims and have the assistant answering on your machine in ten minutes.ArchitectureOne Worker, one claim contract, ports for the model and the store. How a turn flows end to end.GuidesAdd a capability or a tool, generate claims, change the contract, swap the model or the store.EmbeddingDrop the assistant into another claims system as one tag that is handed the claim on screen.TestingOffline unit, integration and end-to-end suites, the scripted model and the coverage gates.ReferenceHTTP API, chat protocol, configuration, and the claim schema, tools and prompts generated from code.
One turn, in three steps
- 1
The page hands over the claim
The claim screen sends the document it is already showing with every turn. The assistant can only ever see that one claim.
- 2
The Worker reads it through tools
A system prompt with the safety rules first, a short brief, then tool calls for the detail: policy, diary, documents, money.
- 3
The answer streams back, with its lookups
Server-Sent Events carry the text, an activity chip per tool, screen highlights and a turn id for feedback.
Built to be extended
Every moving part sits behind one seam. A capability is one object in one file. Prompt text lives in one catalogue. The model is reached through one port, the claims store through another. Adding a capability, a scenario, a model or a store is a matter of adding a file.
npm install
cp api/.dev.vars.example api/.dev.vars
npm run db:migrate
npm run dev # Worker :8787, Vite :5173
npm test # offline, in seconds
npm run test:e2e # real Worker, scripted model