Phase 12
Standalone adoption and release hardening
Finish the install surface, first-run UX, examples, docs, compatibility policy, and release workflow so the product works without reading source.
Roadmap
Build the product around operator trust, not feature theater.
Agent Harness is not trying to become a vague “AI platform.” The current program is tighter: standalone adoption, reliable execution, benchmarkable quality, and only then careful expansion toward shared operation.
Current stance
No hosted plan, no checkout flow, no account gate in this cycle.
The website is here to help users install, evaluate, and understand Agent Harness as a standalone OSS product. Commercial packaging and hosted control-plane concerns are deliberately deferred.
Phase 13
Reliability and evidence-first execution quality
Make crashes, retries, approvals, and recoveries predictable, structured, and explainable from artifacts instead of raw logs.
Phase 14
Retrieval, routing, and benchmark quality
Treat routing and semantic-context improvements as benchmarkable product work instead of intuition or anecdote.
Phase 15
OSS-first expansion toward team operation
Prepare for shared-controller usage without turning the standalone local path into a second-class experience.
Want the concrete details?
The docs site summarizes the product story. The repository roadmap and compatibility notes hold the implementation-level commitments.