Getting started

Hard Fault is distributed through the 0.1.5 GitHub Release as a native BYO bundle. You do not need Python, Rust, uv, a source checkout, or administrator access.

Choose your computer

Computer	Release archive
Apple silicon Mac	`byo-0.1.5-macos-aarch64.zip`
Intel Mac	`byo-0.1.5-macos-x86_64.zip`
64-bit Windows	`byo-0.1.5-windows-x86_64.zip`
64-bit Linux, glibc 2.28+	`byo-0.1.5-linux-x86_64.tar.gz`

macOS — Apple silicon

Run in Terminal:

curl -fsSL https://github.com/JasonPeng2019/BYO-Installer/releases/download/0.1.5/install.sh | sh -s -- \
  --version 0.1.5 \
  --base-url https://github.com/JasonPeng2019/BYO-Installer/releases/download/0.1.5 \
  --sha256 a1c2507509a93738d966bbb446266d2d9ff1fd85f2e9b7df7a7eb67ad6063b92 \
  --allow-unsigned

macOS — Intel

Run in Terminal:

curl -fsSL https://github.com/JasonPeng2019/BYO-Installer/releases/download/0.1.5/install.sh | sh -s -- \
  --version 0.1.5 \
  --base-url https://github.com/JasonPeng2019/BYO-Installer/releases/download/0.1.5 \
  --sha256 9896706ab6f94fd6254e55016428c8eff6dd71e579b5d91a52398ac7f56e678e \
  --allow-unsigned

Windows — x86-64

Run in PowerShell:

& ([scriptblock]::Create((irm https://github.com/JasonPeng2019/BYO-Installer/releases/download/0.1.5/install.ps1))) `
  -Version 0.1.5 `
  -BaseUrl https://github.com/JasonPeng2019/BYO-Installer/releases/download/0.1.5 `
  -Sha256 ccbfb0d2f38570cb9417ad80f95e1429dc947ec2aea651a0c65a204ed707908e `
  -AllowUnsigned

Linux — x86-64, glibc 2.28+

Run in a POSIX shell:

curl -fsSL https://github.com/JasonPeng2019/BYO-Installer/releases/download/0.1.5/install.sh | sh -s -- \
  --version 0.1.5 \
  --base-url https://github.com/JasonPeng2019/BYO-Installer/releases/download/0.1.5 \
  --sha256 bb96c01d5ad896835cd5db5126c67d172b5cd55393dab3a678613acc750cde00 \
  --allow-unsigned

The installer downloads the archive over HTTPS, checks it against the pinned SHA-256, and refuses to continue on any mismatch. The digest is fixed in the command itself, so a corrupted or swapped download cannot pass.

Launcher location and PATH

The default launcher locations are:

Platform	Launcher
macOS/Linux	`$HOME/.local/bin/byo`
Windows	`$env:LOCALAPPDATA\BYO\bin\byo.exe`

Installation adds BYO to PATH automatically. On macOS and Linux, open a new terminal after installation. On Windows, the inline PowerShell command makes byo available immediately; restart any other terminal apps that were already open. A global uninstall reverses only the PATH edit BYO recorded.

Initialize a firmware project

The native runtime is installed once per computer. Initialize each project that should use the MCP server:

cd /path/to/your/firmware-project
byo init --dry-run
byo init
byo codex firmware
# Or launch Claude:
byo claude firmware

The dry run is optional. byo init creates the project capsule, installs the managed Codex and Claude projections, registers the project, and runs its health check. The clients then start the compiled MCP server automatically through byo mcp serve; you normally do not run that server command yourself.

Initialize a project without changing directories by supplying its path:

byo init --project /path/to/your/firmware-project

Restart an already-open Codex or Claude session so it reloads the new MCP configuration.

Next steps

Read MCP server & tools to understand how the client starts the server and which tool families it exposes.
Follow Bench bring-up before operating on new hardware.
Use Uninstall BYO to remove one project’s integration, purge one project’s dedicated BYO data, or completely purge the installation.