Autoharness

AutoHarness

[](#requirements) [](#requirements) [](Cargo.toml) [](LICENSE) [](#test) [](SECURITY.md)

Badges are declared facts, not CI output. There is no hosted pipeline: the GPUI shell needs a Metal toolchain, so the gate in [CONTRIBUTING.md](CONTRIBUTING.md) runs locally and is what those numbers come from.

A macOS-only coding-agent control center. Accepts one objective through coordinator chat, routes it to direct execution, a bounded loop, a swarm, or a dynamic DAG, and orchestrates installed Codex or Claude CLI sessions — all local, no external writes. See `PLAN.md` for the full product plan, and [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for how the pieces fit.

**Status: all local V1 phases are complete in code.** Foundation, engine bridge, sandbox, durable queues, direct chat, router and loops, graphs and swarms, replayable review surfaces, memory/evolution, the true-black cockpit, and release hardening ship together. Release hardening covers data integrity, export, privacy purge, diagnostics, semantic keyboard/VoiceOver accessibility, native attention, universal packaging, and a fail-closed signed-update path. Production signing, notarization, and update-feed hosting still require the owner's external credentials. A raw interactive PTY is intentionally outside AutoHarness's structured-agent scope; captured ANSI check output and classified unified diffs are built in.