01Events
One reasoning layer for any system
Route software events, device signals, and direct requests into the same agent runtime through a small HTTP surface.
A reasoning runtime for software, devices, and machines.
Arbiter turns events into stateful, supervised actions. Route work, consult durable memory, execute tools, and observe every decision from one open-source runtime.
02Control
Runtime-level supervision
An advisor model the executor cannot bypass. CONTINUE / REDIRECT / HALT is enforced before a final response ships.
03Memory
Memory that ranks
Tiered retrieval with reranking — a higher-accuracy path and a low-latency path. Pick the tier per call.
04Deploy
Local, cloud, or hybrid
Run models at the edge, route harder decisions to cloud providers, and keep credentials and operational context off constrained devices.
Interactive · TUI
$ arbiterA multi-pane terminal you live in.
Persistent panes for chat, memory, fleet, and tool tail — visible at the same time, not behind subcommands. Background loops stream into a tail pane while you keep typing in the foreground.
- Vim-style motions, fuzzy command palette, no mouse needed.
- Independent conversations per pane.
- Session restore per cwd.
agent · session titlestatus/stats
streamed model output, tool-call summaries, /cmd
results, system messages …
[3 tool calls…]
❯user input here, multi-line if it wraps
esc interrupt · pgup/dn scroll · /agents · /help
One-shot · scriptable
$ arbiter --send "…"Pipe-friendly for any workflow.
Send a single turn from a shell, get the answer on stdout, exit. Drops cleanly into Make targets, git hooks, CI steps — anywhere you already shell out.
- Same agents and memory as the TUI.
- Streams tokens to stdout; exit code reflects the gate.
- Cron-friendly — no terminal needed.
arbiter --send "audit auth flow" --agent index
Reviewing the login handler…
Two race conditions in /login:
1. session token written before validation.
2. logout race on concurrent refresh.
gate: continue ✓ · $0.0021 · exit 0
Server · HTTP + SSE
$ arbiter --apiThe API any client can consume.
Multi-tenant reasoning server on :8080. Ingest events, orchestrate direct requests, manage agents and memory, and stream every decision over SSE.
- OpenAPI 3.1 spec, versioned at
/v1/. - Pluggable billing via
ARBITER_BILLING_URL. - Cancellable requests via
/v1/requests/:id/cancel.
arbiter ↗ POST /v1/orchestrate
agent: index message: "audit auth flow"
request_receivedreq_8s3z
stream_startindex · depth 1
tool_call/parallel (3 children)
tool_call/mem read (consulted 4)
gateverdict: continue ✓
doneok=true · 1.4s · $0.0021
Capabilities
Everything between an event and an action.
Arbiter ships event routing, durable execution, structured memory, delegation, supervision, and versioned outputs as runtime primitives—not glue code around a model call.
Event routing
Match structured hardware and software events to specialized agents by type, or target an agent directly from the source.
Learn moreDurable execution
Every turn is journaled. Drop the connection mid-stream, reconnect with a sequence cursor, and pick up exactly where you left off — nothing re-run, nothing re-billed.
Learn moreStructured memory
A queryable graph of memory entries and relations — not a flat vector dump. Agents read, write, and rank across it as the workflow runs.
Learn moreAgent-to-agent delegation
Agents spin up sub-agents and fan work out in parallel. The whole tree streams back as one ordered event sequence.
Learn moreVersioned artifacts
Durable, addressable outputs. Every file or document an agent produces is versioned and diffable — not lost when the turn ends.
Learn moreMCP tool servers
Connect Model Context Protocol servers once and the runtime exposes their tools to every agent — no per-agent wiring.
Learn moreOpen source
Build from source. Ship from the terminal.
The runtime is open source — clone, build, run. Or grab a pre-built native binary. The TUI, one-shot CLI, and HTTP server all share the same agents, memory, and event model.
Read the docs