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
..
…
…

AWS deployment development tools

This directory contains experimental, account-scoped deployment and cleanup helpers, plus fixtures used to test the service on AWS. These scripts are not a generic production installer. Some intentionally bind to a particular owned experiment; inspect their configuration and ownership checks before use.

For application deployment, start with the AWS guide and the ows CLI. Setup identity and workload permissions are separate. Use reviewed, project-scoped identities and explicit account/region targeting; do not give agent workloads installer credentials.

Local checks

The deterministic tests exercise ownership checks, fixture validation, bounded cleanup and report handling without provisioning cloud resources:

node --test harness/task-desk/server.test.mjs deploy/aws/cleanup.test.mjs deploy/aws/qualification.test.mjs deploy/recovery/backup.test.mjs

Live execution additionally requires authenticated AWS access, an owned deployment, reviewed permissions, budget/expiry controls and an independent cleanup path. Local tests do not establish those prerequisites. Do not run cleanup or provisioning commands against shared/customer resources.

Files and reports

Infrastructure templates, image builders and workload fixtures remain with the code that consumes them. Runtime credentials, Terraform state and generated reports belong in private, ignored state directories. Never commit those outputs. See service deployment for the reusable container and Helm configuration.