UHP is an Apache-2.0, versioned HTTP specification for driving complete agent harnesses as shared infrastructure, standardizing how an application starts a task, streams progress, continues a session, cancels work, and retrieves the files a harness produced.
UHP claims the serving lane between an application and a coding harness, the same lane the LangChain Agent Protocol opened for served agents, and its adoption bet is deliberate: a conformant server must accept the OpenAI Responses request subset, so existing Responses clients work against a UHP server unchanged.
What it is #
An HTTP contract with three roles: a Client (a product backend, CLI, CI job, or another agent) sends work to a Server, and the Server drives one or more Harnesses, complete agent runtimes identified by stable bases such as codex, claude-code, or hermes.
Conformance is cumulative across three classes (Core, Extended, Full), tested by a runnable conformance suite the project publishes, and the machine-readable schema ships as OpenAPI 3.1 plus JSON Schema 2020-12.
A configured harness (base plus model, system prompt, tool restrictions, skills, and budgets) is a first-class addressable object, so a product can retune its agent without redeploying its backend.
Apache-2.0, maintained in the HarnessRouter repository under a maintainer-led, proposal-first process (UEP issues) where the specification, the reference implementation, and the conformance suite must move in the same change.
Status #
Active and shipping fast: 2,994 stars (2026-10-13), 486 forks, created 2026-08-09, pushed 2026-11-16, as of 2026-11-16 (GitHub API).
The spec is at version 2026-10-19, its fifth version in roughly ten weeks (2026-08-11, 2026-09-12, 2026-09-28, 2026-10-04, 2026-10-19), and the conformance suite at the implementing product’s latest tag is 2026.10.19.post9 per the v0.41.17 release notes, with the protocol changelog page’s newest suite entry still 2026.10.19.post6, whose B-01 through B-06 cover the fifth version’s new session_branching capability (re-fetched 2026-11-17).
The fifth version’s changelog has kept growing since: its newest entry adds conditional updates, where a harness read may carry an ETag and its update an If-Match so a stale client write is refused 412 precondition_failed, the sixth capability added within the same version without a version bump (fetched 2026-11-14).
The implementations page lists three servers and one client: HarnessRouter Community Edition (the 2,959-star open-source runner putting Codex, Claude Code, and Hermes behind the contract), the hosted HarnessRouter service (sixteen harness bases with a console and billing), and SuperQode (62 stars as of 2026-10-11), a harness-engineering framework that speaks UHP both as a server and as a client, which makes it the spec’s one second implementation. The community footprint is the weak signal: the Show HN launch drew 10 points (2026-08-17) and a Hacker News search for the protocol’s name returns zero stories (2026-10-08), so the 2,959 stars measure the implementing product, not the spec’s reach.
Strengths #
- Responses-API compatibility is a distribution strategy, not a detail: products with existing Responses clients, SDKs, and stream parsers gain a harness lane with no client rewrite, which is the cheapest on-ramp any serving spec in this index offers.
- The conformance suite is the definition of conformant, and servers that pass may say so with a version and class, which most young specs never operationalize.
- The three-artifact rule (spec, reference implementation, and suite move together) is a governance discipline that keeps specification sentences enforced.
- Coding-agent-native vocabulary: harnesses, bases, configured harnesses, skills, and MCP servers are first-class objects, so the spec reads like the stack this corpus covers rather than a generic model API.
Cautions #
- Five spec versions in roughly ten weeks, with a same-day patch to the fourth, mean the draft churn this category penalizes elsewhere is present here at full intensity, so pinning is a real cost.
- The spec lives in the repo of the company that sells the hosted HarnessRouter service, with no foundation above the maintainer’s UEP process, so the steward and the commercial winner are the same party.
- The community footprint is thin: one 10-point Show HN thread, no independent coverage found, and the one second implementation sits at 62 stars.
- The lane is contested: the LangChain Agent Protocol, every cloud provider’s agent-serving API, and the Responses API itself all compete for the same integration surface.
Pricing #
The specification, the conformance suite, and HarnessRouter Community Edition are free and Apache-2.0. The hosted HarnessRouter service is separately priced by HarnessRouter with a free tier (no figures cited here), and a conformant UHP server can run wholly on your own machine with your own keys, so hosting cost is optional by design.
Compared to #
- Agent Protocol (LangChain): the serving-lane neighbor; the Agent Protocol standardizes runs, threads, and schemas for agents you serve, while UHP drives complete coding harnesses you already run and is deliberately Responses-compatible so existing clients keep working.
- ACP: editor-to-agent over local stdio for one editor session; UHP is application-to-server over HTTP for products that embed harnesses at distance.
- Agent Host Protocol: both are client-to-infrastructure specs, but AHP synchronizes live session state across many clients while UHP dispatches tasks and retrieves artifacts.
Bottom line #
Recommended for teams embedding coding-agent harnesses in their own products who want one HTTP contract across harness vendors and can absorb draft-version churn. Not for editor-hosted agent sessions, which is ACP’s lane, and not for agent-to-agent delegation, which is A2A’s. My disagreeable claim: the Responses API already owns this lane by gravity, so the open question is not whether UHP’s wire compatibility is right but whether one name, one conformance suite, and one governance doc can claim a surface the industry is otherwise treating as an OpenAI API extension.
Changes #
- 2026-10-08 - Created from the 2026-10-08 entrant scan (the harness-serving slot), with the four-versions-in-eight-weeks churn and the vendor-repo stewardship recorded as the central cautions.
- 2026-10-11 - Re-verification: refreshed stars and forks as of 2026-10-11; the spec remains at its 2026-10-04 fourth version with no fifth version since, and SuperQode remains at 62 stars.
- 2026-10-16 - Re-verification: the conformance suite gained two more protocol-neutral patches through 2026.10.4.post11 (2026-10-15) while the spec stays at its 2026-10-04 fourth version with no fifth version, and the implementing product’s release train moved to v0.34.1 (2026-10-15).
- 2026-10-17 - Re-verification: the implementing product’s release train moved again to v0.34.2 (2026-10-16) while the spec stays at its 2026-10-04 fourth version with no fifth version.
- 2026-10-18 - The implementing product’s release train moved to v0.35.0 and v0.35.1 (both 2026-10-18) while the spec stays at its 2026-10-04 fourth version with no fifth version, the suite’s newest entry still the protocol-neutral 2026.10.4.post11 (2026-10-15).
- 2026-10-19 - The spec moved to its 2026-10-19 fifth version (the harness models view’s
fallbackdeprecated), its fifth in roughly ten weeks, and the conformance suite was repackaged for it (2026.10.19.post1 at the implementing product’s latest tag, spec-matching again). - 2026-10-20 - The Cautions lead moved to the five-versions-in-ten-weeks count the Status section records, aligning the churn statement with the 2026-10-19 fifth version.
- 2026-10-22 - The implementing product’s release train moved from v0.35.1 to v0.35.15 (2026-10-21 and 2026-10-22) with v0.36.0 release candidates tagged, and the conformance suite at its latest tag moved to 2026.10.19.post3 (the protocol-neutral T-12 step-budget addition); the spec stays at its 2026-10-19 fifth version.
- 2026-10-24 - The v0.36.0 release candidate went stable (2026-10-23) and the release train moved through v0.36.3 (2026-10-24); the spec stays at its 2026-10-19 fifth version and the conformance suite at 2026.10.19.post3.
- 2026-10-25 - The release train moved to v0.36.4 (2026-10-25) and a v0.37.0 release-candidate series opened behind it (rc.1 through rc.10, 2026-10-24 to 2026-10-25); the spec stays at its 2026-10-19 fifth version and the conformance suite at 2026.10.19.post3.
- 2026-10-26 - The v0.37.0 release candidate went stable (2026-10-26) and a v0.37.1 release-candidate series opened behind it (rc.1 and rc.2, 2026-10-26); the spec stays at its 2026-10-19 fifth version and the conformance suite at 2026.10.19.post3. Corrected the star-history chart markup (the light-theme source carried the dark-theme parameter; it now points at the default chart).
- 2026-10-27 - The v0.37.1 release candidate went stable (2026-10-26) and the release train moved through v0.37.6 (2026-10-27); the spec stays at its 2026-10-19 fifth version and the conformance suite at 2026.10.19.post3.
- 2026-10-31 - The release train moved through v0.37.9 (2026-10-29) to v0.37.13 (2026-10-31) and the conformance suite moved to 2026.10.19.post4 (2026-10-29), which covers the spec’s new create-time Idempotency-Key capability (
harness_idempotency); the spec stays at its 2026-10-19 fifth version, so the suite’s addition is a capability of the fifth version rather than a sixth. - 2026-11-01 - Re-verification: the spec stays at its 2026-10-19 fifth version with the conformance suite at 2026.10.19.post4 (the changelog’s newest entry), the release train still ends at v0.37.13 (2026-10-31), and the repository pushed 2026-11-01 on housekeeping only (an opt-in security-scan CI workflow and a kit rename, no new tag).
- 2026-11-03 - The release train moved through v0.37.14 (2026-11-01) to v0.37.15 (2026-11-03) while the spec stays at its 2026-10-19 fifth version and the conformance suite at 2026.10.19.post4 (the changelog’s newest entry unchanged); the repository pushed 2026-11-03.
- 2026-11-04 - The release train moved through v0.37.16 and v0.37.17 (2026-11-03) and v0.37.18 (2026-11-04) to v0.38.0 (2026-11-04), and the conformance suite moved to 2026.10.19.post5, which covers the fifth version’s new input_requests capability (a task can end its turn by asking the person, with secret answers reaching the harness outside the conversation and appearing nowhere a client reads); the spec stays at its 2026-10-19 fifth version; the repository pushed 2026-11-04.
- 2026-11-06 - The release train moved to v0.38.1 (2026-11-04, a security fix that ends group-root reach in session file reads and writes, and a task that cannot start now says so at once) and v0.38.2 (2026-11-04, a licensing correction that removes an LGPL image library from the shipped console image and corrects NOTICE), while the spec stays at its 2026-10-19 fifth version and the conformance suite’s newest entry stays 2026.10.19.post5 (2026-11-03); the repository pushed 2026-11-06 on runner hardening (a turn answers only the session that started it, and a turn’s idempotency key dedupes within its own session only).
- 2026-11-08 - The release train moved through v0.38.3 (2026-11-07, the MCP-server connection probe now joins an event’s
data:lines before reading them, answers capped at 4 MiB and 30 seconds, and Pi and Oh My Pi take custom Responses-format connections) and v0.38.4 (2026-11-07, on deployments shared by several organizations the model broker’s per-organization connections are address-checked the way MCP server addresses already were) to v0.38.5 (2026-11-08, first-start harness installs pinned to exact versions with committed digests, connection-level request headers for AI gateways such as Cloudflare’s, and optional per-step workspace checkpointing), while the spec stays at its 2026-10-19 fifth version and the conformance suite at 2026.10.19.post5; the repository pushed 2026-11-08. - 2026-11-12 - The release train moved through v0.38.6 and v0.38.7 (both 2026-11-08, bug and dependency security fixes in the harnesses’ own dependencies) to v0.39.0 (2026-11-09, a session can branch from an earlier response, matching the spec’s new session_branching capability, and Roder joins as an opt-in harness), v0.40.0 through v0.40.3 (2026-11-09, memories by default for new agents, prompts off the command line and onto stdin, runner hardening with its tests in CI), and v0.41.0 through v0.41.13 (2026-11-09 to 11-12, memories polish and first-start installs that run nothing they downloaded as root), while the spec stays at its 2026-10-19 fifth version and the conformance suite moved to 2026.10.19.post6 (2026-11-04, B-01 through B-06 covering session_branching, the fifth version’s newest capability addition, #477); the repository pushed 2026-11-12.
- 2026-11-14 - The release train moved from v0.41.13 through v0.41.14 and v0.41.15 (both 2026-11-13, session processes starting through setpriv with a scrubbed environment and stored MCP secrets bound to the server they were saved for) to v0.41.16 (2026-11-14, a console rail rename), and the spec changelog gained a sixth capability addition within the 2026-10-19 fifth version (a harness read may carry an ETag and its update an If-Match, with a stale version refused 412 precondition_failed) while the suite stays at 2026.10.19.post6; the spec remains at its fifth version; the repository pushed 2026-11-14.
- 2026-11-17 - Re-verification: the release train moved to v0.41.17 and v0.41.18 (both 2026-11-16: memories owned by the API keys that minted them #700, Gemini thinking tokens billed as output #691, harness-model menus naming a key the harness can use #697, harness exports leaving out the instance’s self-served tools #702, and the Graphiti revise-or-forget deletion found by the suite’s ME-05 and ME-06 with
hr_-prefixed schema names reserved #701, plus a release-gate fix #705), the conformance suite moved to 2026.10.19.post9 per the v0.41.17 notes (the EN-07 environment-read checks riding along) while the protocol changelog page’s newest suite entry stays post6, the spec changelog’s newest addition stays the ETag/If-Match one, and the spec remains at its 2026-10-19 fifth version; the repository pushed 2026-11-16.
See also #
- Agent Protocol (LangChain) - the other serving spec in this category, and UHP’s closest comparison point
- Agent Client Protocol (ACP) - the editor-to-agent lane UHP deliberately does not occupy
- Protocols Feature Matrix - the category comparison this note joins as the twelfth column
- Agentic Coding Tools Landscape - the map of the harnesses UHP exists to drive
References #
https://github.com/HarnessRouter/harnessrouter/tree/main/protocol - the spec home: current version 2026-10-19, draft-standard status, conformance suite, governance and versioning links
https://unifiedharnessprotocol.org/ - the official site: version history (2026-08-11, 2026-09-12, 2026-09-28, 2026-10-04, 2026-10-19) and the specification chapters
https://github.com/HarnessRouter/harnessrouter - repository facts: 2,994 stars, 314 forks, Apache-2.0, created 2026-08-09, pushed 2026-10-14 (GitHub API, as of 2026-10-13)
https://raw.githubusercontent.com/HarnessRouter/harnessrouter/main/protocol/IMPLEMENTATIONS.md - the implementations page: HarnessRouter CE and hosted servers, SuperQode server and client, listing criteria
https://raw.githubusercontent.com/HarnessRouter/harnessrouter/main/protocol/versions/2026-10-04/architecture.md - the Client/Server/Harness roles, the three conformance classes, and the configured-harness object model
https://raw.githubusercontent.com/HarnessRouter/harnessrouter/main/protocol/GOVERNANCE.md - the UEP proposal-first process and the three-artifact rule
https://raw.githubusercontent.com/HarnessRouter/harnessrouter/main/protocol/CHANGELOG.md - the spec-churn record: the 2026-10-04 same-day patch, the conformance-suite additions through 2026.10.19.post6, the 2026-10-19 fifth version’s deprecation and input_requests entries, and the session_branching capability addition (#477)
https://github.com/HarnessRouter/harnessrouter/releases - the implementing product’s release train: v0.39.0 (session branching, Roder), the v0.40.x memories wave, and v0.41.x through v0.41.18 (fetched 2026-11-17)
https://github.com/SuperagenticAI/superqode - the second implementation, 62 stars, Apache-2.0 (GitHub API, as of 2026-10-11)
https://harnessrouter.ai - the hosted service: sixteen harness bases behind the UHP contract, commercial with a free tier
https://hn.algolia.com/api/v1/search?query=%22Unified%20Harness%20Protocol%22&tags=story - the footprint scan: zero stories naming the protocol, found 2026-10-08
https://hn.algolia.com/api/v1/search?query=%22HarnessRouter%22 - the Show HN launch thread at 10 points (2026-08-17)