Quesarby MLAI

Start

ABI runtime, as the tree actually ships.

Nightly Rust orchestration, wrappers, crates, and what a successful gate actually proves.

Use the wrappers

The public ABI tree is nightly Rust. Bare cargo is the wrong entry. ./tools/cargo.sh pins the toolchain the tree actually builds with. ./tools/check.sh is the primary validation gate.

WDBX is a required sibling. Clone both workspaces. A successful gate is evidence for that checkout and environment, not for a hosted product or a foundation-model quality claim.

donaldfilimon/abi
git clone https://github.com/donaldfilimon/wdbx
git clone https://github.com/donaldfilimon/abi
cd abi
./tools/cargo.sh --version
./tools/check.sh
./tools/cargo.sh build -p abi-cli

These commands are copied from the README. This page does not execute them.

Crates you can inspect

abi-cli is the operator surface. abi-mcp speaks JSON-RPC 2.0 over stdio with optional loopback HTTP. abi-ai holds an exact model registry and template completion. abi-sea selects bounded evidence for a context. abi-gpu reports capability and returns accelerated=false when native kernels are not linked.

Local template completion does not establish model quality. Persistence defaults to $HOME/.abi/wdbx and can be disabled with ABI_WDBX_PERSIST=0.

  • abi backends — list what this process actually reports
  • abi scheduler status — health for this process, not a fleet view
  • abi dashboard --once --plain — one-shot text, no hosted UI implied
  • abi plugin list — plugins the current binary loaded under contract
  • abi wdbx query — retrieve from the local store
  • ABI README

    Source description, tool commands and stated limitations; not a reproduced test run.

Checked against these sources on .

Start

ABI runtime

ABI is a Rust framework for local AI orchestration, semantic vector storage, and GPU capability reporting. Build the CLI and MCP server with the repository's pinned toolchain and the ./tools/cargo.sh wrapper.

donaldfilimon/abi
# Validate the Rust workspace
./tools/check.sh
# Build the CLI and MCP server
./tools/cargo.sh build -p abi-cli -p abi-mcp

# Inspect capabilities and terminal surfaces
./target/debug/abi backends
./target/debug/abi dashboard --pane system --once --json
./target/debug/abi agent tui
Runtime
Rust workspace: AI, WDBX, GPU, MCP, terminal
Configuration
Crate-specific Cargo features
Capability inspection
abi backends · abi wdbx gpu info

  • abi-ai

    Profile routing, completion, and governance helpers.

  • abi-sea

    Evidence selection, scoring, and learning loop.

  • abi-wdbx

    Durable memory and retrieval from the sibling Rust substrate.

  • abi-gpu

    Backend reporting, optional Metal DOT kernels, and CPU fallback.

  • abi-mcp

    JSON-RPC tool handlers and stdio server.

  • abi-cli

    Commands, agent REPL, and diagnostics dashboard.

Design decisions

Inspectable capabilities

Report the selected backend and whether acceleration is active. Capability detection alone is not evidence of accelerated execution.

Bounded evidence

SEA selects evidence within record, token, cluster, and prompt-byte budgets. Retrieval is distinct from model training.

Explicit runtime boundaries

Local completion is deterministic persona-template generation. Live HTTP completion requires an explicitly configured provider.

All docsPrevious: Different tools. Clear roles.Next: Fail closed. Tag the figure.
Architecture

Next

Developers

The READMEs these articles cite.