Arbiter

Introduction

Arbiter local development control plane documentation

Arbiter

Arbiter is a local-first Linux control plane for understanding, diagnosing, and safely operating local development projects, Docker/Compose resources, host processes, ports, files, and multi-service environments.

It strictly adheres to an observe → diagnose → propose → approve → act → verify workflow and binds its REST API to 127.0.0.1 by default.


Quick Start

# 1. Setup environment and install dependencies
cp .env.example .env
uv sync --all-extras

# 2. Start the Arbiter daemon
uv run arbiter serve

# 3. Verify health and port listeners
curl http://127.0.0.1:8765/health
curl http://127.0.0.1:8765/api/v1/ports

Open http://127.0.0.1:8765 to access the Web Control Panel.


Interfaces & Integrations

Arbiter provides consistent, safety-backed operational capabilities across multiple interfaces:

Interface / ProtocolCommand / EntrypointDescription
Web Control Panelhttp://127.0.0.1:8765Interactive topology canvas, observability, container logs/metrics, approvals, and admin.
Terminal UI (TUI)arbiter tuiFast, keyboard-driven terminal dashboard (like lazydocker/k9s) with vim navigation.
CLI & Fuzzy Pickersarbiter <command>fzf-style interactive selectors for projects, ports, containers, and approvals.
Shell Prompt Hookarbiter promptStatus pills in zsh, bash, fish, or Starship prompts.
Model Context Protocolarbiter mcpNative stdio MCP server for Claude Desktop, Cursor, Zed, and Antigravity.
Agent-to-Agent (A2A)/.well-known/agent-card.jsonInter-agent discovery and task delegation protocol.
REST & Event APIs/api/v1/*Standard REST endpoints, SSE activity stream, and NDJSON streaming agent query.

Core Capabilities

  • Live Machine Topology: Real-time relational graph linking projects, Compose files/services, containers, images, volumes, networks, ports, host processes, Dockerfiles, and Make targets.
  • Port Conflict Reconciliation: Deterministic port collision detection and automatic free-port reassignment across .env and compose.yaml with backup and rollback.
  • Multi-Project Stacks: Named environment profiles with 1-click context switching, topological DAG boot ordering (Kahn's algorithm), and multi-probe readiness gates (tcp_port, http_get, docker_health).
  • Config & Secrets Intelligence: Proactive detection of port drift and missing .env variables compared to .env.example, with zero raw secret exposure and time-travel visual diffs.
  • Safety Engine: 5-tier risk classification (READ_ONLY to DESTRUCTIVE), immutable serialized approval payloads, and independent post-action verification.

Documentation Navigation

On this page