Skip to main content

Crates

Generated by harness-docs from cargo metadata --no-deps: every package of the workspace, with the description its Cargo.toml gives. There are 11 packages. None is on a registry; build them from the repository. The crates they depend on live in their own repositories, each pinned by tag or revision: the tool, model-client and MCP crates in the workspace Cargo.toml, the confinement crates in crates/harness-substrate/Cargo.toml and the specification crates in crates/harness-conformance/Cargo.toml.

PackageDirectoryIn RustWhat it is
b10x-harness-app-servercrates/harness-app-serveruse b10x_harness_app_serverServes the b10x loop over the pinned Codex app-server JSON-RPC format
b10x-harness-cataloguecrates/harness-catalogueuse harness_catalogueOne catalogue of tools, published to every harness under three verbs, over the tools crates' operations
b10x-harness-clicrates/harness-cliuse b10x_harness_cli, binary b10x-harnessThe b10x harness, driven from the command line
b10x-harness-conformancecrates/harness-conformancebinary b10x-harness-conformanceESS conformance against native Harness library boundaries
b10x-harness-llmcrates/harness-llmuse harness_llmThe b10x harness's model port over llm's client crates, and the credential sources that feed them
b10x-harness-loopcrates/harness-loopuse b10x_harness_loopThe b10x agent loop: turn assembly, tool round trips, approvals and budgets
b10x-harness-mcpcrates/harness-mcpuse b10x_harness_mcpReviewed MCP tool snapshots as a Harness ToolPort
b10x-harness-substratecrates/harness-substrateuse b10x_harness_substrateA client of the substrate wire: what this machine can confine, and the tools that answer
b10x-harness-wirecrates/harness-wireuse b10x_harness_wireNeutral values and ports shared by the b10x agent loop and its model wires
b10x-harness-xtaskcrates/harness-xtaskbinary b10x-harness-xtaskThe repository's own gate and contract checkers, run as cargo xtask
harness-docscrates/harness-docsuse harness_docs, binary harness-docsGenerates the derived pages of the Harness documentation site (CLI, toolchains, crates, status), checks every page, and binds a built site to its commit