01Memory
Memory that compounds.
Typed, temporal memory stores decisions, references, feedback, and artifacts so agents start with context instead of rediscovering it.
Turn model calls
into managed
agent workflows.
Arbiter runs multi-agent workflows from a TUI, one-shot CLI, or HTTP+SSE server with live-streamed execution, durable memory, artifacts, and advisor gates built into the runtime.
Supported providers and models
- Claude Opus 4.7
- Claude Sonnet 4.6
- Claude Haiku 4.5
- GPT-5.5
- GPT-5.4
- GPT-5.4 mini
- o4-mini
- Gemini 3.1 Pro
- Gemini 3 Flash
- Gemini 3.1 Flash-Lite
- Nano Banana 2
- Nano Banana Pro
- nemotron3
- qwen3.6
- kimi-k2.6
- granite4.1
02Supervision
Supervision the agent can't bypass.
Advisor gates run at the runtime layer. Final answers can continue, redirect, or halt before they reach the user.
03Surfaces
Every action is visible
Stream tool calls, memory reads, sub-agent output, artifacts, and gate decisions over SSE into the TUI, HTTP clients, or your own UI.
On the wire
What the runtime actually streams.
Every turn surfaces as structured SSE events: lifecycle, sub-agent fan-outs, tool calls, memory reads, advisor gate verdicts. The web app reads this stream — same as your client would, same as the docs say.
See the event catalogHow it differs
Everything around the model call, already handled.
| Capability | Arbiter Runtime | Agent frameworks | Model APIs | DIY |
|---|---|---|---|---|
| One binary for TUI, CLI, and HTTP | Yes | library only | No | build it |
| Structured stream of every agent step | Yes | varies | tokens only | build it |
| Advisor gates at the runtime layer | Yes | custom code | No | build it |
| Memory and artifacts across turns | Yes | bring storage | No | build it |
| Sub-agent delegation with ordered events | Yes | custom code | No | build it |
| Provider routing from one agent surface | Yes | varies | provider only | build it |
Open API
Drive it from any stack.
The same runtime can run locally, from scripts, or behind a documented HTTP endpoint. Stream responses with SSE, manage agents and memory, execute tools, and route across providers with one bearer-token API.
Read the API docsPOST /v1/orchestrateSSE · OpenAPI 3.1
curl -N http://127.0.0.1:8080/v1/orchestrate \
-H "Authorization: Bearer $ARBITER_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"agent": "index",
"message": "Audit the auth flow for race conditions."
}'Get started
Clone it. Run it. Wire it into your stack.
Start with the local install, then expose the same runtime over HTTP when you need another client to drive it.
Install locally