Skip to content
  • Keep runtime truth boundaries consistent across implementation, design docs, and OpenAPI spec
  • Keep hardening the OAP release/install path: release tarball / registry install, clean-install smoke, runtime assets and WebUI asset packaging checks
  • Evaluate more aggressive recovery strategies (auto-requeue / resume) as needed; currently fail-closed only
  • Deferred capabilities remain candidates, not commitments: Unix socket model runtime, first-class action_run / artifact

OAP (Open Agent Harness Personal) still exposes the same OAH-compatible API. The local personal deployment path is oah daemon, a SQLite/local-disk profile, embedded workers, and shared WebUI/TUI/Desktop clients.

Only these release-engineering items remain tracked here:

  • Desktop distribution hardening: macOS signing / notarization, auto-update, daemon supervisor panel, endpoint profile switcher, installer smoke tests
  • Package publishing: decide which @oah/* packages stop being private, define npm / registry publishing order and version sync rules
  • Pre-release gates: clean-install smoke, packed tarball content checks, runtime assets / WebUI assets / server entrypoint checks
  • Supply-chain hardening: package signing, SBOM, release provenance

The repository root no longer maintains separate ROADMAP.md files or long phase notes.

Current status and forward direction now live in the docs site: