The run loop
You talk to one orchestrator. A full run can add a planner, acceptance-bar teacher, parallel workers, reviewer and final gate. The team exchanges explicit JSON artifacts under .harnes/runs/.
Artifacts
plan.jsondefines lots and non-overlapping waves.bar.jsondefines acceptance criteria and required evidence.- Worker reports include implementation and test outcomes.
- Review and gate records preserve findings and readiness.
Architecture
The desktop app uses Tauri and SolidJS. Rust crates implement terminal panes, threads, telemetry, policy guards, worktrees, memory review, evaluation and the crew engine. SQLite stores local threads and searchable context.
The documented source build targets Windows 11. Cross-platform distribution is not yet claimed.
Safety model
harnes is a control plane, not a security sandbox. Runtime guards can allow, ask or deny tool actions. Blocking permission requests surface to the human. Secrets are redacted before telemetry storage, and commits remain proposals.
Provider adapters
The repository includes provider configuration for several coding CLIs. Non-default adapters are best-effort and can require flag updates as upstream CLIs change. Compatibility should be proven through a smoke run before relying on a provider for production work.