TL;DR: faf-cli now compiles to standalone binaries for macOS, Linux, and Windows. No Node.js. No Bun. No npm. Download the binary, run it. Same distribution model as Claude Code.
What Changed
Bun's bun build --compile takes 800 modules of TypeScript and produces a single executable. The entire faf-cli — all 64 commands, the Mk3.1 scoring engine, bi-sync, TURBO-CAT, everything — in one file.
Why This Matters
Before today, faf-cli required Node.js or Bun installed on your machine. That's a runtime dependency. It means:
- CI/CD pipelines need Node.js configured
- Docker images need a runtime layer
- New developers need to install npm first
Now? Download the binary. Run it. Done.
The Claude Code Pattern
Claude Code ships as a Bun compiled binary. faf-cli now does the same. Same toolchain, same distribution model, same developer experience.
Verified
Every command was smoke-tested against the compiled binary:
faf initfaf git <url>faf autofaf gofaf bi-syncfaf scoreAll six produce identical output to bunx faf-cli. The full test suite — 1,143 tests across 50 suites — passes clean.
Get It
Download from GitHub Release:
curl -L https://github.com/Wolfe-Jam/faf-cli/releases/
download/v5.0.6-bun/faf-darwin-arm64 -o faf && chmod +x faf Or install the traditional way:
npm install -g faf-cli bunx faf-cli auto The Numbers
- v5.0.6 — Released March 14, 2026
- 1,143/1,143 — Tests passing
- 4 platforms — macOS ARM64/x64, Linux x64, Windows x64
- 800 modules — Bundled into one executable
- 100% — Trophy score
The Roadmap
This is Phase 2 of the Bun alignment strategy:
- Phase 1 —
bunx faf-cli autoverified (done) - Phase 2 — Compiled binaries (done, you're reading it)
- Phase 3 —
bun:ffito call Rust Mk4 natively - Phase 4 — WASM Mk4 parity everywhere
Rust defines. Bun delivers. WASM runs everywhere.