Docs

What works today (Unfix 0.1.1)

  • Hosts: Windows 10/11 with Docker Desktop running Linux containers, and Linux with Docker Engine. Verification builds execute in a Linux container. Fresh Windows CI validates wheel installation, doctor diagnostics and demo creation; the complete Windows Docker verdict path still needs a Docker Desktop host check.
  • Builds: Automatic project setup detects CMake/CTest and Make. A project can provide explicit build and test shell commands in unfix.yaml (or legacy cplus.yaml). Other build systems have no automatic setup.
  • Toolchains: The packaged C/C++ image has GCC, Clang, CMake, Ninja, GDB and Valgrind. Host compilers are not used for container verification.
  • Checks: Baseline and patched builds, regression tests, AddressSanitizer, ThreadSanitizer and repeat/revert checks are implemented. UBSan reports can be parsed when a check requests UBSan; automatic project verification does not promise a UBSan gate.
  • Bugs: Deterministic, memory, race, flaky and timeout reproduction are represented in BugSpec and exposed by unfix bug. A verdict depends on completed evidence; a timeout is not itself proof of a fix.
  • Changes: Working tree, branch, commit and patch are accepted by CLI/TUI. A pull request can be checked through the GitHub Action.
  • Interfaces: Interactive terminal UI, CLI with JSON output, and MCP over stdio. Install the supplied wheel locally and use CLI/TUI/MCP; there is no partner GitHub Action yet.
  • Boards: ST-Link/pyOCD support for STM32 NUCLEO targets, with the NUCLEO-F401RE firmware demo and physical board acceptance path. Board results require on-target checks; MCP does not claim board verification.
  • Data: Runs, BugSpecs and HTML reports stay on the partner's machine. Verification itself makes no LLM calls and has no Unfix cloud service. An optional external coding agent uses its own service. Dependency downloads follow the manifest allowlist and are audited.

Not supported yet

  • A verified installation with no internet access; this has not been tested.
  • A complete Linux-container verification on a fresh GitHub-hosted Windows runner, which has no Docker Desktop Linux daemon.
  • Automatic discovery of Meson, Bazel or arbitrary vendor firmware builds.
  • A public PyPI package, public release, or GitHub Action installable by partners without access to the private repository.
  • MCP proof of a physical board fix; use local board commands instead.