Native Rust CLI for creating, running, inspecting, and packaging Agentic Harness workspaces.
The CLI stays Cargo-native: it invokes Rust workspaces directly instead of bundling JavaScript or a TypeScript runtime.
agentic-harness guide --workspace .
agentic-harness doctor --workspace . --json
agentic-harness code --workspace . --llm auto --prompt "Fix the failing tests"
agentic-harness score --workspace . --run latest
agentic-harness inspect --workspace .Use guide for the shortest setup path, doctor for readiness, code for the
coding-agent loop, score for run quality, and inspect for the latest run
summary.
agentic-harness new <path>scaffolds a Rust Agentic Harness agent project.agentic-harness start,wizard,tui, oruiopens the guided local TUI.agentic-harness guideprints the setup-to-coding path.agentic-harness doctorchecks workspace readiness;checkis an alias.agentic-harness dashboardshows workspace status;statusis an alias.agentic-harness coderuns the coding-agent loop.agentic-harness scoreevaluates a coding run and can gate CI with--fail-below.agentic-harness inspectreads the latest coding-run summary.agentic-harness templatemanages reusable template packs;templatesandtplare aliases.agentic-harness setup llm,setup sandbox, andsetup hostinginstall local prerequisites.agentic-harness sandboxruns configured sandbox file and shell operations.agentic-harness hostinginspects or starts local HTTP hosting.agentic-harness dev --workspace <path> --port 3583runs the Rust agent server in development and restarts it when workspace files change.agentic-harness run <agent> --workspace <path> --id <id> --payload '<json>'invokes one agent.agentic-harness serve --workspace <path> --addr 127.0.0.1:3583serves the Rust app over HTTP.agentic-harness manifest --workspace <path> [--cloudflare]prints generic agent metadata or Cloudflare Worker routing metadata.agentic-harness add <model|sandbox|mcp> --printprints native Rust connector instructions.agentic-harness package,smoke, andrelease-checkcover release packaging and validation.
Built-in starters are:
hello, triage, data, coding, code-review, test-fixer, docs-writer,
refactor-agent, release-agent, repo-analyst, support
Create and run one:
agentic-harness new ./review-agent --template code-review
agentic-harness run code-review --workspace ./review-agent --id demo \
--payload '{"prompt":"Review the current changes","checks":["cargo test"]}'Native build:
agentic-harness build --workspace <path> --target native --output <path>Node host package:
agentic-harness build --workspace <path> --target node --output <path>Cloudflare Worker boundary build:
agentic-harness build --target cloudflare \
--workspace <path> \
--output <path> \
[--worker-app app.js] \
[--worker-wasm app.wasm] \
[--worker-wasm-crate <path>]This writes non-proxy Worker boundary files: _entry.js, wrangler.jsonc,
cloudflare-manifest.json, agentic_harness_worker.js,
agentic_harness_app.js, agentic_harness_app.d.ts, and optionally
agentic_harness_app.wasm.
The Cloudflare build target is not a full deployment runtime yet. It emits the
Worker routing, Durable Object config, SQL session plumbing, and event response
shim, while handler execution still requires a Worker-compatible Rust/WASM app
adapter. Use --worker-app <path> to copy that adapter into
dist/agentic_harness_app.js; use --worker-wasm <path> to copy its companion
WASM module into dist/agentic_harness_app.wasm.
dist/agentic_harness_app.d.ts describes the adapter context and exports. When
--worker-wasm is used without --worker-app, the CLI generates a default JSON
ABI adapter for agentic_harness_alloc, agentic_harness_invoke,
agentic_harness_last_result_len, exported memory, and optional
agentic_harness_init. Use --worker-wasm-crate <path> to build that WASM from
a Rust crate with
cargo build --release --target wasm32-unknown-unknown --no-default-features.