Two layers that should not be mixed
The UHP ecosystem is still small. HarnessRouter's product ecosystem is already broader. This page tracks both, but labels them separately so a new provider integration or starter kit is not misreported as adoption of the UHP standard.
UHP protocol ecosystem
| Component | Current role |
|---|---|
| UHP specification | Normative HTTP contract; current published version 2026-08-11. |
| HarnessRouter Community Edition | Self-hosted reference implementation; latest observed tag v0.8.3 (23 Aug 2026). |
| HarnessRouter Cloud | Hosted implementation named by the UHP project. |
| Conformance suite | Defines behavioral verification classes and test expectations. |
| Independent third-party server | Not established by this tracker as of 23 August 2026. |
| SuperQode (SuperagenticAI/superqode) | Third-party UHP client: consumes UHP servers as a client (UHPClient, UHPHarnessProtocolAdapter, superqode connect uhp; targets 2026-08-11). A client, not a UHP server and not a conformance result. See the adoption tracker. |
| SourceShift mini-ork (SourceShift/mini-ork) | Independent UHP client transport (in progress): provider kind uhp, stdlib-only direct HTTP transport for UHP 2026-08-11. Client-side only; not a UHP server. See UHP clients. |
HarnessRouter implementation ecosystem
Within the Community Edition build, several distinct layers should be kept apart:
- Harness backends: Claude Code, Codex, Hermes, Pi and DeepSeek Harness (
dsh). HarnessRouter integrates each behind its UHP implementation; that is not proof the upstream project adopted UHP natively. - Model-provider integrations: Anthropic, OpenAI, OpenRouter, Azure Foundry, Amazon Bedrock, TokenRouter, Vercel AI Gateway and LLMTR. These are connection paths with compatibility varying by backend.
- Product surfaces: starter-kit examples such as Slides, Sheets, Dashboards and Videos.
These integrations answer “what can HarnessRouter run with?” They do not change what a conformant UHP server is required to implement.
Starter-kit product examples
| Kit | What it demonstrates |
|---|---|
| Slides | An agent product that creates editable presentation objects through a conversation-driven workflow. |
| Sheets | Row-oriented workflows where harness-backed agent columns can process structured inputs. |
| Dashboards | Agent-built database queries and visual panels against connected data sources. |
| Videos | Planning, rendering and arranging generated clips and media on a timeline/canvas workflow. |
Adjacent interoperability standards
- MCP: tool, resource and context access at a different boundary. See UHP vs MCP.
- A2A: communication and collaboration between independent agent systems. See UHP vs A2A.
- ACP (Agent Client Protocol): standardizes editor/UI-to-agent interaction — a different boundary than UHP. See UHP vs ACP.
- Harness Protocol: a separate project centered on portable harness configuration through
harness.yaml. - Agent Harness Protocol (AHP): a separate supervision/policy-oriented protocol project.
What would count as real ecosystem growth?
- An independent UHP server passes conformance testing.
- A product client interoperates with multiple UHP server implementations.
- A harness vendor publishes native UHP support.
- Independent SDKs or libraries emerge with cross-server interoperability evidence.
- Conformance reports are published across separately maintained implementations.