Skip to content

Arbiter 0.1.0 (pre-release)

Pre-release
Pre-release

Choose a tag to compare

@TheAuditorTool TheAuditorTool released this 30 Oct 06:40
· 17 commits to main since this release

v0.1.0

The first public pre-release of Arbiter, the command center above your AI tools: an early build for early
adopters, and the rough edges found here shape v1.

Before you start

  • Arbiter needs a license. During the pre-release it is free: ask for one at arbitermcp.com, and the email
    brings your key. Activate it in the app's first screen or with arbiter activate.
  • Windows will warn that it protected your PC, because this build is not code-signed yet: choose More info,
    then Run anyway. Every download is listed with its SHA256 in a SHA256SUMS file signed with the Code Reality
    Labs release key, so you can check what you got.

Added

  • A desktop app (Windows, Linux) with pages for Home, Overview, Chat, Runs, Sessions, Tickets, Activity,
    Brief, MCP, Projects, Channels, Seats and Config. The Auditor and Curator pages appear when TheAuditor or
    Curator is installed beside it.
  • One program, arbiter: the daemon (arbiter daemon), the MCP server for your coding agents
    (arbiter mcp), and the commands for projects, runs, tickets, settings, accounts, seats, schedules, the
    license, telemetry, 2FA and the service (arbiter project, arbiter run, arbiter ticket and the rest;
    arbiter <command> --help describes each one).
  • A local daemon that dispatches, supervises and recovers work across coding clients, provider APIs and a
    local model. Its control surface is a named pipe on Windows and a Unix socket on Linux; no network port is
    opened unless you enable the HTTP control plane or Telegram's webhook mode.
  • Tickets: a work list joined to what your terminals provably did, with phases, estimates from closed tickets,
    and MCP tools so your agents can file and update them.
  • Cost-aware routing of each job to Claude Code, Codex, a provider API or the local model, with the decision
    and its reasons recorded.
  • Terminals for Claude Code and Codex that survive their window and can be driven remotely: owned consoles on
    Windows (or tmux inside WSL, if you choose that host), tmux on Linux.
  • Remote control from Telegram, with Signal and WhatsApp in beta: allowlisted users may read status. Once a
    channel is configured, two-factor approval is on by default: anything that runs code or sends a prompt needs
    a TOTP code from an enrolled authenticator, and is refused until one is enrolled.
  • Seats: switch the logged-in Claude account without logging out, by hand or, when enabled, automatically
    before the active one runs dry, with a usage forecast.
  • arbiter service install starts Arbiter at sign-in: a per-user entry on Windows, and on Linux a systemd user
    unit it writes and enables. arbiter service start|stop|status controls it.
  • arbiter doctor checks this machine (including whether it can run the terminals it is configured for), and
    arbiter doctor --bundle collects versions, masked settings, recent logs and error references for a bug
    report; arbiter error-lookup shows the details behind an error reference.

Security

  • All state is kept in SQLCipher databases whose keys are bound to this machine and user. Security modes add
    a license-held key fragment; the credentials database is only openable online in those modes.
  • Settings that decide who may drive the machine, what it runs or where secrets go need a 2FA code once an
    authenticator is enrolled. Wrong codes are rate-limited: the sixth within 15 minutes locks further attempts
    for 15 minutes, doubling with each further lockout up to a day.
  • Secrets are never shown back by the app or the CLI, and arbiter settings set reads them from a hidden
    prompt or stdin.
  • The HTTP control plane is off by default, refuses keys shorter than 16 characters and requires TLS to listen
    beyond this machine.

Telemetry

  • Telemetry shows a notice before anything is sent. The default level, lite, sends counts, durations, error
    types and an abstract routing record; it never sends prompts, code, file names, paths, project names or
    keys. arbiter telemetry off stops all of it, and arbiter telemetry status lists every field.
  • Licensing is not telemetry: the license is checked in with the license server, and a seat you add talks to
    its provider with the login you gave it.

Requirements and known limitations

  • Windows 10 or 11 (x64), or Linux x64. On Linux Arbiter needs glibc 2.34 or newer, and the desktop app needs
    WebKitGTK 4.1. macOS is not supported yet.
  • The local model runs on your graphics card through Vulkan, so it needs a graphics driver with Vulkan
    support. It is not bundled: arbiter setup-llm downloads it.
  • Claude Code and Codex are installed separately; Codex 0.158 or newer is required.
  • This is a pre-release: the databases are versioned and migrate forward, but interfaces may still change.