Files
Rohit PrasadandDevika Verma d53e058eda Introduce OpenWorker Harness SDK (in beta), agent service cluster and relevant developer documentation (#844)
Allow developers to easily build AI apps without worrying about the harness part.
Bundles the Rust agent runtime as a SDK (Rust and TypeScript) for building desktop and web applications. Applications can manage a local harness or connect to an authenticated harness service on k8s with separately scaled workers and sandbox execution.

The implementation is primarily contained in harness/, with deployment tooling in deploy/, Markdown guides in docs/harness/guides/, and the static documentation site in docs-site/. It does not replace the existing Python harness or migrate OpenWorker Desktop.

Co-authored-by: Devika Verma <devikaverma11@gmail.com>
2026-11-06 09:45:20 -08:00
..

Python/native harness contracts

compaction.json contains 15 reviewed pure-policy cases plus exact prompt strings, pinned to public Python c37b761. known-deviations.json explicitly records P1–P3 from docs/harness/PYTHON-RUST-PARITY.md. Fixing those Python bugs should make the reference adapter fail until their expected differences are reviewed/removed. Do not refresh goldens automatically or broadly xfail failures.

Run from repository root:

PYTHONDONTWRITEBYTECODE=1 ../openworker/.venv/bin/python harness/tests/python-contract.py
cargo test --manifest-path harness/Cargo.toml --workspace --locked

The Python command uses a development environment only, fake providers and temporary state. Rust tests consume the same fixture data. Neither invokes a live provider. The fixture set is an initial shared subset, not proof of full Python/Desktop parity. Runtime-specific fault tests cover additional native durability/retry/isolation behavior independently.