arbiter

agent
Security Audit
Fail
Health Warn
  • License — License: Apache-2.0
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Low visibility — Only 6 GitHub stars
Code Fail
  • exec() — Shell command execution in agents/backend.json
  • network request — Outbound network request in agents/backend.json
  • exec() — Shell command execution in agents/frontend.json
  • exec() — Shell command execution in agents/reviewer.json
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

A local, mixture-of-agents (MoA) runtime in a single native binary.

README.md

Logo

Arbiter

A local agent runtime in a single native binary.
Local-first; network optional.
About · Download · Documentation · Contributing

Arbiter session sidebar and inline diff rendering

Run multi-agent workflows on your machine — interactive TUI, one-shot CLI, or HTTP+SSE — with hard tool allowlists and a shared streaming event bus.

Quick start

# Install (macOS arm64)
curl -L https://github.com/tylerreckart/arbiter/releases/latest/download/arbiter-macos-arm64.tar.gz \
  | tar xz -C /usr/local/bin

export OPENROUTER_API_KEY="sk-or-..."   # or use Ollama — see docs
arbiter --init                          # seed starter agents under ~/.arbiter/
arbiter                                 # open the TUI

Linux binaries, source builds, Ollama, --send, and --api are in
getting-started/local.

Same agents, three faces

Mode Command For
Interactive arbiter Multi-pane TUI, global conversation store
One-shot arbiter --send <agent> "..." Scripts, cron, CI
Server arbiter --api HTTP+SSE API, tenant-isolated, A2A v1.0

One binary. Shared storage under ~/.arbiter/. Provider keys (OpenRouter, Ollama, …) are the only external dependency for model calls.

Why run it

  • Own the harness. Orchestrate specialists, durable memory, and tool use without duct-taping a chat CLI to FastAPI and SQLite. The runtime stays thin; agent behavior lives in constitutions (JSON: model, role, rules, tool allowlist).
  • Hard limits, not prompt suggestions. Every agent's tool surface is an allowlist checked at dispatch. Optional advisor gate: a second model signs off before consequential turns reach you.
  • One event model everywhere. The orchestration loop streams the same SSE-shaped events the TUI already consumes — text, tool calls, files, sub-agent responses, done. API clients get that stream over the wire; durable request logs make reconnect and replay possible.
  • Route work in, don't write a dispatcher. Webhooks, queues, firmware, and sensors can POST /v1/events; declare a glob per agent and Arbiter routes matching events there.

Documentation

Arbiter is experimental. The event surface, agent constitutions, and HTTP shape may change. /exec is unsandboxed by default; treat it accordingly.

Licensed under the Apache License 2.0.

Reviews (0)

No results found