Unified Harness Protocol news

Latest: v0.8.2/v0.8.3, session isolation, SuperQode client adoption (23 August 2026)

Classification first: two new official tags were verified — v0.8.2 (session write-wall, scratch compatibility, Hermes vision routing; commit-documented Full-class 52/52 run) and v0.8.3 (self-host share-link fix), both 23 August 2026. The UHP protocol remains 2026-08-11 and the conformance suite remains 2026.8.11.post1 with 52 checks. Separately, SuperQode (SuperagenticAI/superqode) is verified as an independent third-party UHP client: implementation code confirms UHPClient, UHPHarnessProtocolAdapter and superqode connect uhp, targeting UHP 2026-08-11 with discovery, tasks, streaming, continuation, cancellation and idempotency keys. That is client adoption — not an independent UHP server, not server conformance, and not vendor-native adoption.

A correction to yesterday's item: reachability verification against the tags shows the conformance-suite revision, error-envelope fix, Hermes relay normalization and dsh reasoning_effort handling all shipped with v0.8.1; they were mislabelled "unreleased" here on 22 August. The genuinely unreleased main work as of 23 Aug is Claude Code plugin support (--plugin-dir materialization plus stdio MCP configuration, merge 95b96d7) — HarnessRouter integration, not Anthropic adoption of UHP.

Post-v0.8.0 hardening and tag v0.8.1 (22 August 2026)

Classification first: everything below is HarnessRouter implementation and conformance-suite development. It is not a UHP protocol release — the protocol remains 2026-08-11. One new official tag was observed, v0.8.1 (21 August 2026, server-side workspace registry). These were labelled unreleased at the time; see the 23 August correction above — they ship with v0.8.1.

• Conformance-report honesty: suite revision 2026.8.11.post1 makes the JSON verdict strict — a skipped check is no longer counted as conformance (conformant vs conformant_with_skips), skipped checks are enumerated in skipped_not_verified, and reports now carry suite_version and generated_at. Total checks remain 52.
• Hermes integration fix (now known to have shipped in v0.8.1): a loopback relay normalizes OpenAI-legal-but-translator-fatal message shapes before the provider sees them; the provider credential stays in the runner. Documented patched full-class runs: 52/52 through TokenRouter and LLMTR.
• DeepSeek Harness aggregator fix (now known to have shipped in v0.8.1): reasoning_effort rejections from aggregators are retried once without the parameter and then stripped for the turn; a documented LLMTR run improved from 47/52 to 52/52.
• Failed Response schema correction (now known to have shipped in v0.8.1): the error envelope on a failed Response now carries a spec-valid type/code pair; previously every failed turn produced a spec-invalid Response.

No upstream harness project announced UHP involvement in this window; native adoption remains Not established for OpenAI/Codex, Anthropic/Claude Code, Nous/Hermes, Pi and DeepSeek.

Independent clients (23 Aug): SourceShift mini-ork landed aaf22c3, adding a uhp provider kind — a stdlib-only direct HTTP transport for UHP 2026-08-11 with SSE parsing, bearer auth, previous_response_id continuation via a session sidecar, and real-server tests. Self-described "B1 of UHP adoption": a verified independent client transport, integration maturity in progress. Together with SuperQode's verified UHP client (unchanged since 22 Aug), UHP now has two independently implemented clients. Evidence and boundaries: UHP clients & independent implementations; protocol positioning: UHP vs ACP.

Timeline

What changed after the launch?

The fastest movement has been in the reference implementation, especially backend integrations (Pi and DeepSeek Harness), provider integrations, media routing and starter-kit product surfaces. That pace is useful evidence that HarnessRouter itself is active, but it should not be confused with independent UHP adoption.

What has not changed?

• The published UHP protocol version remains 2026-08-11.
• Native UHP adoption by OpenAI/Codex, Anthropic/Claude Code, Nous/Hermes, Pi or DeepSeek Harness is not established by primary vendor evidence reviewed for this tracker.
• A separately maintained third-party UHP server with published conformance evidence is not yet recorded here.

Where to follow each signal

Use the release tracker for version-by-version changes and the adoption tracker for independent implementation or vendor-support evidence. This page summarizes only developments that materially change the picture.

Primary sources

• HarnessRouter official tags
• Official UHP protocol directory
• Official UHP site