Examples
Example implementations of the Unified Harness Protocol, grouped by the role each fills. Listings are community-maintained by pull request and do not imply endorsement or certification — the only conformance claim that means anything is passing the conformance suite.
Example servers
A server runs one or more harnesses behind the contract. Guide: Implement a server.
Open-source runner that puts existing harnesses — Codex, Claude Code, Hermes — behind the UHP contract. HarnessRouter · Apache-2.0.
Harness-engineering framework whose own harness speaks UHP natively through superqode serve uhp, binding one configured HarnessSpec. SuperagenticAI · Apache-2.0.
Example clients
A client drives a UHP server. Guide: Implement a client.
Harness-engineering framework that connects to a UHP server via superqode connect uhp. SuperagenticAI · Apache-2.0.
Listing criteria
A listing is a factual row, not a certification. Open a pull request against this file in the repository adding one card. To merge, an entry needs:
- A public, usable release — a repository or a product page, not an announcement.
- The UHP version the implementation targets.
- A maintainer contact reachable from the linked page.
- The role it fills: Server (runs harnesses behind the contract), Client (drives a UHP server), SDK (a library for building either), or a combination.
A conformance level appears on a listing only once UHP publishes reproducible
test evidence for that implementation; until then, absence of a level is
expected, not a mark against the entry. The evidence is a report produced by
the conformance-measure workflow and landed under conformance/reports/<slug>/;
give your card id="<slug>" and the site shows the measured level and badge on
it, generated from the report. How to get measured, and the badge to embed, are
on the conformance page.
Building an implementation? Start with Implement a server or Implement a client.