Independent server
uhp-go: independent UHP server
uhp-go is a public, separately maintained UHP server and client implementation in Go. Its checked-in evidence establishes independent server conformance against the prior 62-check suite, while current UHP main has since moved to 63 checks.
What is verified
Section titled “What is verified”aenawi/uhp-go is a public Go implementation of UHP maintained outside HarnessRouter. Its README describes the project as an independent implementation that is not affiliated with, endorsed by, or supported by HarnessRouter. It ships both a server (uhpd) and a client (uhpc).
The repository’s checked-in conformance page records a live 62/62 Full run with 0 failed, 0 skipped and 0 errored on 31 August 2026 against UHP 2026-08-11, suite package 2026.8.11.post1, pinned to HarnessRouter commit 1176d9a5175fa0938d4c2e43ccbbdaab621d8030. That run used the claude-code harness and no explicit --model.
That is meaningful ecosystem evidence: a separately maintained public server implemented the protocol and passed the complete suite shape that existed at the measured revision. It is not a HarnessRouter backend or wrapper claim.
Current-suite boundary: UHP main is now 63 checks
Section titled “Current-suite boundary: UHP main is now 63 checks”HarnessRouter PR #55, merged after the recorded uhp-go run, adds Full check R-08. R-08 directly enforces the existing Sessions §5 sentence that a bodyless POST /v1/sessions/{session_id}/share publishes the session. The earlier R-series helper retried a rejected bodyless request with {"enabled": true}, so a toggle-only implementation could pass R-01 through R-07 while still rejecting the protocol’s bodyless form.
Current suite shape is therefore 63 checks: Core 40, Extended +8 and Full +15. The package revision remains 2026.8.11.post1; UHP remains 2026-08-11.
PR #55 records a pre-merge 63/63 Full, zero-skipped measurement against an independent Go UHP server with R-08 passing on a bodyless publish. The PR body does not name that server repository, so this guide does not attribute that 63/63 result to uhp-go by name. uhp-go’s own checked-in conformance page still records the earlier 62/62 run pinned to 1176d9a.
This distinction matters: uhp-go is verified as an independent server with published complete evidence for the 62-check revision; current-main 63-check evidence exists for an independent Go server, but the upstream source does not identify the repository.
What uhp-go implements
Section titled “What uhp-go implements”The public README currently lists these shipped harness bases:
claude-codecodexgrok-cliopencodepi
The server exposes UHP over HTTP, persists task/session state with embedded SQLite, supports bearer-key authentication, and shells out to locally installed harness CLIs. The project also ships uhpc, a UHP client intended to work against conformant servers generally rather than only against uhpd.
The checked-in documentation describes session sharing, files/artifacts, task execution, continuation, cancellation, harness configuration and conformance reproduction. Those are implementation facts about uhp-go; they do not make any of the upstream harness vendors native UHP adopters.
Why this changes the ecosystem picture
Section titled “Why this changes the ecosystem picture”Before this evidence was recorded, this guide could verify independent UHP clients but not a separately maintained server with complete suite evidence. uhp-go crosses that independent-server implementation threshold for the measured 62-check revision.
What is still not established:
- a checked-in uhp-go 63/63 report against current HarnessRouter
main; - a published cross-server client matrix showing the same independent client interoperating with both HarnessRouter and uhp-go;
- native UHP adoption by Claude Code, Codex, Grok CLI, OpenCode or Pi merely because uhp-go can drive them;
- any certification body or endorsement relationship between uhp-go and HarnessRouter.
Evidence chronology
Section titled “Evidence chronology”| Date | Evidence | What it proves |
|---|---|---|
| 31 Aug 2026 | uhp-go commit 46af340 and checked-in docs/conformance.md: 62/62 Full, zero skipped, pinned to HarnessRouter 1176d9a | Complete independent-server conformance for the then-current 62-check suite shape |
| 31 Aug 2026 | HarnessRouter PR #55 / merge 08d61ea: R-08 added, suite becomes 63 | Bodyless share publication is directly measured instead of hidden by compatibility retry |
| 31 Aug 2026 | PR #55 pre-merge measurement: 63/63 Full, zero skipped against an independent Go UHP server | Current-suite independent implementation evidence; repository not named in the upstream PR body |
Related pages
Section titled “Related pages”Read conformance for the current 63-check shape, adoption for claim classification, ecosystem for implementation roles, UHP clients for independently maintained clients, and HarnessRouter for the reference implementation.