Skip to content
hard-faulthard-fault

Hard Fault documentation

Hard Fault is a local embedded-debug and firmware agent built around pyOCD, Stage 0 validation tooling, and an MCP server. It flashes images, reads UART, and drives SWD on a real board, with a multi-provider “brain” that plans and runs actions behind safety guardrails.

Where to go next

Section titled “Where to go next”
  • Getting started — install the native BYO bundle from GitHub Releases, initialize a project, and launch Codex or Claude with the MCP server.
  • Uninstall BYO — remove one project’s integration, purge one project’s dedicated BYO data, or completely purge BYO.
  • Bench bring-up — host setup and Stage 0 validation for a board on your bench.
  • Supported boards — the targets it runs on today.
  • Providers & auth — pick and authenticate a model backend.
  • MCP server & tools — the governed tool surface.
  • Guardrails — flash gates, recover gates, and watchers.

Two ways to drive it

Section titled “Two ways to drive it”
  • byo codex firmware — launch Codex with the project’s managed firmware mode.
  • byo claude firmware — launch Claude with the same project and MCP runtime.

Run byo init once in the project first. Both clients then start the same compiled MCP sidecar through byo mcp serve and use the same governed action surface.