ENGINEERING · September 29, 2026 · 3 min read

ABI Is Rust Now: What Changed, and What Didn't

The ABI runtime moved from Zig to a nightly-Rust workspace on July 30, 2026, and WDBX became its own sibling workspace in August. Here is what that means for anyone building from source.

By MLAI Research

On July 30, 2026 the ABI runtime landed on main as a nightly-Rust workspace, and the Zig tree was torn down the same day. Two of the posts below, on Zig 0.16 and on why WDBX was written in Zig, describe the implementation that replaced. They stay up for provenance and are marked historical.

This note covers what a reader building from source needs to know. It makes no performance claim: there is still no published benchmark harness, and a language change is not evidence that anything got faster.

One gate, one wrapper

The ABI README names two entry points. ./tools/check.sh is the validation gate: policy tests, formatting, clippy with warnings denied, the workspace build and tests, and docs. ./tools/cargo.sh is the Cargo wrapper that selects the pinned nightly toolchain. Bare cargo is the wrong entry, because it may pick a different toolchain than the tree builds with.

A green gate is evidence about that checkout on that machine. It is not evidence about a hosted product, a mobile build, or model quality.

WDBX is a sibling, not a subdirectory

On August 22 the WDBX crates were extracted into their own workspace with history preserved. They keep the abi- crate prefix on purpose, and ABI builds against them through relative Cargo paths, so the two repositories must be cloned side by side.

The WDBX V2 documentation set published in June describes an earlier single-crate project. It remains downloadable from the docs, labelled as a snapshot, and the current wdbx README is the authority for the substrate.

The MCP surface

abi-mcp exposes twelve contract-covered tools over stdio. Since September 23 its optional loopback HTTP listener also serves persistent MCP 2024-11-05 HTTP+SSE sessions with optional bearer auth. It is not the newer Streamable HTTP transport, and this website does not expose those tools to visitors.