About this UHP developer guide
This is an independent technical publication. It is not the official Unified Harness Protocol site and is not affiliated with HarnessRouter.
Page reviewed 4 Oct 2026 Source and review policy
Purpose
Section titled “Purpose”The site explains UHP for developers, tracks implementation evidence and places the protocol in the wider agent-infrastructure landscape. It links back to primary sources so readers can distinguish normative requirements from interpretation.
Independence
Section titled “Independence”Unified Harness Protocol is initiated and led by HarnessRouter. This site is independently published and does not represent HarnessRouter, OpenAI, Anthropic, Nous Research or other projects named in the guide.
Editorial method
Section titled “Editorial method”- Prefer primary specifications, repositories and vendor documentation.
- Date fast-changing claims.
- Separate reference-implementation support from native vendor adoption.
- Correct pages when the protocol or evidence changes.
- Avoid presenting inference as a verified fact.
Content status
Section titled “Content status”The guide began with a 15 August 2026 source baseline. Living references and integration guides now carry their own review dates; historical reports keep the original versions, denominators and source cutoffs. A later page edit does not mean every cited experiment was rerun.
Use the guide for your decision
Section titled “Use the guide for your decision”The homepage’s task paths provide an orientation gateway when you have not selected a boundary yet. Choose the work you need to accomplish, then carry the relevant contract and evidence into the detailed guide.
| Reader task | Useful starting point | Evidence to carry onward |
|---|---|---|
| Learn the execution boundary | What is UHP? | Client, server and harness responsibilities |
| Build a client or server | Getting started and specification | Supported version, class, capabilities and actual response semantics |
| Select a runtime | Ecosystem and the relevant integration guide | Adapter pin, upstream interface and workload-specific limitations |
| Assess an adoption or test claim | Adoption and conformance | Who made the claim, against which version, and what was actually demonstrated |
This publication adds explanation and decision guidance. Use a versioned primary contract for implementation, then verify your actual server/configuration. A source-backed guide is useful preparation, not evidence that your deployment or provider account is ready.
Publication corrections should identify the route, disputed sentence, primary source and version/date; the editorial policy explains the evidence needed. For a defect in UHP itself, use the upstream issue tracker and its proposal process. This static site has no submission form.
Related reading
Section titled “Related reading”For the evidence rules behind these pages, read the editorial and verification policy. The adoption tracker separates implementation evidence from native upstream adoption.
The guide homepage offers entry paths by reader task. Use the dated news archive to understand what changed at a particular point, then follow its current reference links before making an implementation decision. The privacy policy describes the static site, browser features and owner-configured third-party scripts.