<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>UHP Developer Guide Updates</title>
<link>https://unifiedharnessprotocol.dev/</link>
<description>Independent Unified Harness Protocol release, adoption and technical updates.</description>
<language>en</language>
<lastBuildDate>Sun, 08 Nov 2026 05:06:55 GMT</lastBuildDate>
<atom:link href="https://unifiedharnessprotocol.dev/feed.xml" rel="self" type="application/rss+xml"/>
<item>
    <title>Three HarnessRouter releases in six hours, and MCP's Skills extension moved to Beta</title>
    <link>https://unifiedharnessprotocol.dev/news/</link>
    <guid isPermaLink="false">uph-2026-11-08-releases-and-extension-stages</guid>
    <pubDate>Sun, 08 Nov 2026 05:06:55 +0000</pubDate>
    <description>HarnessRouter stable is now v0.38.5 from 52c929f1cf30, published 8 November at 04:35:16 UTC, with development main at the same commit the tag was cut from. Three releases landed in about six hours: v0.38.3 joins a multi-line MCP server answer before reading it, reads at most 4 MiB and 30 seconds, and releases the session-bound turn status, cancel and idempotency dedupe tracked as development evidence on 6 November; v0.38.4 holds an organization's own model-broker connection address on a shared deployment to the same outside-the-deployment rule an MCP address follows, refusing unusable addresses before any lookup and answering 403 with the reason; v0.38.5 pins and stamps every first-start harness install against committed digests, adds request headers on a connection, and can save a sandbox's tool steps as a task runs. In the rotation cluster, MCP's extension-lifecycle SEP-3392 is Final and the Skills extension specification moved from specification/stable/ to specification/beta/ on 29 October, so its stage is Beta even though SEP-2640 is Final, and ACP's Client-Provided System Prompt RFD completed on 6 November, stabilizing the systemPrompt field on session setup.</description>
</item>
<item>
    <title>The harness pages stopped calling September current</title>
    <link>https://unifiedharnessprotocol.dev/news/</link>
    <guid isPermaLink="false">uph-2026-11-07-harness-current-coordinates</guid>
    <pubDate>Sat, 07 Nov 2026 05:13:44 +0000</pubDate>
    <description>Twenty-three pages still named HarnessRouter's stable release as v0.18.1, v0.18.2, v0.18.4 or v0.19.0 with eleven, twelve or thirteen released backends, and still called UHP 2026-09-12 with 75 conformance checks the current line. The current stable is v0.38.2 with 30 backends, and the published draft is 2026-10-19 with 104 checks; the dated measurements behind each sentence were left as recorded and only the claim about now was corrected. Hermes released v0.23.0 on 5 November and five pages now name it as the current stable; DeepSeek Harness moved from dsh-v0.2.2-alpha.2 to dsh-v0.2.2-rc.1, the first release candidate of the 0.2.2 series; and the client page's SuperQode coordinate moved from v2.5.5 to v2.31.4.</description>
</item>
<item>
    <title>A turn answers only the session that started it</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-11-06-turn-session-isolation</guid>
    <pubDate>Fri, 06 Nov 2026 05:33:00 +0000</pubDate>
    <description>HarnessRouter stable is unchanged at v0.38.2 from 8e1cf1b598a7, and no release has followed it. What moved is development main, now two commits ahead of the tag, and both commits narrow a turn's reach to the session that started it. GET /turn/{id} and POST /turn/{id}/cancel now take the identifier the gateway already sends on every runner call, and a turn started by another session reads as no turn at all (404), while a turn recorded without an identifier answers as before. And the runner's idempotency dedupe map is keyed by session and key, so a retried request from the same session still returns its running turn, while another session that sends the same key starts its own turn instead of being answered with that turn's id, status and model. The 2026-10-19 specification leaves the key's scope to the client - it is a client-generated-unique-string - so a client that reuses one key across sessions is misusing it, and the implementation now contains the mistake rather than the other session's turn. Three corrections went with the run: the /harnessrouter/ page contradicted itself about the upstream main coordinate, the /uhp-vs-acp/ page named claude-agent-acp's current stable as v0.100.0 where the adapter has since published v0.101.0, and the /mcp-tasks/ page carried two facts the published Tasks extension has since corrected - the missing-capability error code is -32021 rather than -32003, and the resultType its examples use is complete. This run's rotation was security and evaluation, and it checked the cluster's primaries rather than finding them moved: the HarnessRisk benchmark's figures are exact against both its pinned repository commit and the arXiv v1 abstract - 128 sandboxed cases, three harnesses, six models and fourteen model-harness configurations, with no revision after v1 of 18 August 2026 - the Qwen Code pull requests behind the managed-runtime-attestation and workspace-trust guides are all merged as recorded, the reference implementation's released security work has not moved since v0.38.2, and MCP's enterprise-managed-authorization extension is unchanged. Nothing else moved: UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post5 with 104 executable checks, the released backend set is still 30 offered bases, and gateway/app.py still sets UHP_VERSION = 2026-09-28. The weekly competitive cohort was not due - it was worked on 2 November for ISO week 45 and is next due in ISO week 46, from 9 November.</description>
</item>
<item>
    <title>HarnessRouter v0.38.0, and the UHP draft gained a way to ask the person</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-11-05-v0.38.0-asking-the-person</guid>
    <pubDate>Thu, 05 Nov 2026 05:40:00 +0000</pubDate>
    <description>HarnessRouter stable is now v0.38.2 from 8e1cf1b598a7, published 4 Nov at 22:53:50 UTC, with development main separately observed at the same commit. Three releases landed in one day and the first is a minor one - v0.38.0 at 07:28, v0.38.1 at 17:29, v0.38.2 at 22:53 - and one changed the protocol itself. The UHP 2026-10-19 draft gained a section the version number does not show: Tasks 3.2 Asking the person. The draft's five chapters changed between v0.37.18 and v0.38.2 - tasks, lifecycle, errors, sessions and streaming - and the spec's own index records the change as added after publication and additive. With the new input_requests capability, a harness that needs one answer ends the turn instead of inventing one: the response ends incomplete with incomplete_details.reason input_required, the question is the response's last input_request item, and the answer is an input_response item on the next task, chained on that response. The turn's last message carries the question as text too, so a client that renders only message items shows it, and a task chained on a response that ended on a question carries either the answer or anything else, which passes the question over. Three refusals name what went wrong with an answer - input_not_pending, input_request_expired and input_response_invalid - and the conformance package moved with it: 2026.10.19.post5, 104 executable checks = 41 Core, 9 Extended, 54 Full, with the two new T-13 and T-14 checks. The credential boundary moved too: in v0.38.0 a remote MCP server's address and credentials stay in the server and the session gets a local address holding one token that stops working when the turn ends, so rotate MCP tokens if an agent you do not fully trust has run on the instance; the same release encrypts stored credentials at rest on every install, keeping the key in /data/secret-key beside the data it protects; v0.38.1 closes a gap where a session's reads and writes kept root's supplementary group, so an agent could use a link to reach what gid 0 can reach, and a volume you mount can hold more; and v0.38.2 corrects the image's licence text after an LGPL library shipped with no licence text beside it. This run's rotation was discovery and execution: the discovery side had not moved, and the execution side carried the day's finding. Nothing else moved: UHP is still 2026-10-19 Draft, the released backend set is still 30 offered bases, and gateway/app.py still sets UHP_VERSION = 2026-09-28. The weekly competitive cohort was not due - it was worked on 2 November for ISO week 45 and is next due in ISO week 46, from 9 November.</description>
</item>
<item>
    <title>HarnessRouter v0.37.18, and two more security releases in one night</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-11-04-v0.37.18-two-more-security-releases</guid>
    <pubDate>Wed, 04 Nov 2026 05:30:00 +0000</pubDate>
    <description>HarnessRouter stable is now v0.37.18 from 433acfe0047e, published 4 Nov at 01:41:17 UTC, with development main separately observed at the same commit. Three releases landed since yesterday, two of them security releases. v0.37.17 closed a critical one: an API key could read any file as root, because a marker file in a session's folder could point the file routes at any folder on the machine and a caller's own PUT could set it, reaching HR_SECRET_KEY, the stored provider keys and the databases; only the value the runner writes itself counts now, and upgrading does not undo a read that already happened and the logs cannot show one, so the release advises changing HR_SECRET_KEY and the console password, replacing the stored provider keys, reissuing the API keys and restarting. The same release makes every file route refuse dot paths, covering the runner's state, git's folder and any credential file such as sub/.env that the listing, the archive and share links used to serve, and stops root from running what the product user can change. v0.37.16 turned off the console's image optimizer, which was reachable with no sign-in through published Next.js remote-code-execution bugs, hardened MySQL and MariaDB connections against a hostile server, stopped a build's own code from planting a link that makes the runner write or read a file as root, sandboxes an agent's HTML and SVG files opened through the console, and ends a relay route with its turn; it also fixed a regression it had introduced the day before, sending Gemini's key both as x-goog-api-key and as a bearer token, so every Gemini turn on a Google API key failed with a 401, and Google API keys no longer offer gemini-3.5-flash because Google answers that id with gemini-3.6-flash. v0.37.18 moved Claude Code's default model to claude-sonnet-5.5. This run's rotation was memory and identity: the UHP Memories chapter is byte-identical across v0.37.14, v0.37.15, v0.37.16, v0.37.18 and main, the 13 ME- checks are unchanged and CE still advertises no memories capability; the rotation's correction was the stable Hermes release, now Agent v0.22.7 after v0.22.6, where the memory-mutation contract the site documents is still present and unchanged, so the guidance stands and only its anchor moved. Nothing else moved: UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post4 with 102 executable checks, the released backend set is still 30 offered bases, and gateway/app.py still sets UHP_VERSION = 2026-09-28. The weekly competitive cohort was not due - it was worked on 2 November for ISO week 45 and is next due in ISO week 46.</description>
</item>
<item>
    <title>HarnessRouter v0.37.15 closes every path from an agent turn to a credential</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-11-03-v0.37.15-turn-to-credential</guid>
    <pubDate>Tue, 03 Nov 2026 05:31:00 +0000</pubDate>
    <description>HarnessRouter stable is now v0.37.15 from d11a20845b6a, published 3 Nov at 03:16:52 UTC, with development main separately observed at the same commit. It is a security release: an agent turn runs with real shell access, and everything it can read is also readable by anything that reaches the agent, such as a prompt injection. Every provider key, including the image-generation credential and the Bedrock and Vertex credentials, now stays in the runner's relay, and a turn receives the relay's address and a placeholder on every base and every connection shape; the relay signs Bedrock requests, mints Vertex access tokens, accepts only a path and never follows a redirect, and a test builds every base's turn with a canary key and fails if the key appears anywhere the turn can read. The instance's own secrets no longer travel with git or the other processes the runner starts for a session, hooks the agent leaves in its repository no longer run, writes stay inside the session's folder with the session's own permissions, jobs for other sessions travel privately, a stored key no longer follows a changed address or provider, and there is no default password any more - an instance without one of its own makes one at first start. Advisories GHSA-cww9-m4gr-cmw5, GHSA-m479-gmx7-8r8h (Omer Bar-Ness, MergeSafe) and GHSA-r37g-f5m3-523c (AkshatJoshi2000) ship with it, with the advice to rotate provider keys after upgrading if untrusted people can start turns or agents read untrusted content. The starter kits are rebuilt with every critical and high advisory closed, and a deck's PowerPoint export now includes its diagrams and code blocks. This run's rotation was interoperability and adjacent protocols: the ACP protocol published v1.15.0 and v1.15.1 with schema-v1.29.1 and schema-v2.0.0-alpha.13, and every change in them is unstable, unstable-v2 or rfd, so the stable-v1 surface this site describes is unchanged; the adapter lines moved to codex-acp v2.5.0 and claude-agent-acp v0.100.0; and the A2A CLI's current stable is v0.3.1, whose release redacts --svc-param values in config show. Nothing else moved: UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post4 with 102 executable checks, the released backend set is still 30 offered bases, and gateway/app.py still sets UHP_VERSION = 2026-09-28. The weekly competitive cohort was not due - it was worked on 2 November for ISO week 45 and is next due in ISO week 46.</description>
</item>
<item>
    <title>HarnessRouter v0.37.14, and NeMo Relay's current stable carries breaking changes</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-11-02-v0.37.14-nemo-relay-0.11.0</guid>
    <pubDate>Mon, 02 Nov 2026 06:28:00 +0000</pubDate>
    <description>HarnessRouter stable is now v0.37.14 from f6592b27e0d4, published 1 Nov at 10:24:02 UTC, with development main separately observed at the same commit. A file the agent deleted is no longer counted as one it made: an agent that deletes a file on a later turn after already handing it back still had that turn list the deleted file as produced, so the session's changed files reported produced: 2 beside a single file, and a deletion is now recognised however it was made. This run's rotation was harnesses, and the weekly competitive cohort was due - 2 November is the Monday of ISO week 45, and the cohort was last visited for week 44 on 26 October. The week-45 pair is /nemo-relay/ and /uhp-vs-mcp/. The /nemo-relay/ route needed a currency correction: NeMo Relay's current stable is 0.11.0 (28 October 2026), after 0.10.4 on 20 October, with 0.11.1-beta.1 a prerelease, and the 0.11.0 line carries breaking changes a reader on 0.9.3 or 0.8.3 needs before upgrading - Node.js requires 24.13.1 or later, LangChain and LangGraph tool results arrive in the typed nemo.relay.tool_result@1 wrapper, coding-agent hooks must be refreshed and restarted with tool checks defaulting to fail-closed and delivery failures returning exit code 2, Relay checks client access before lending provider credentials, and automatic remote OTLP logs and metrics require HTTPS unless explicitly allowed. The /uhp-vs-mcp/ route was rechecked and retained: the released MCP specification is still 2026-07-28 and the Filesystems Working Group's charter still lists SEP: Filesystem Operations for Resources as Ideating. Two harness coordinates were stale: Pi's current release is v1.4.0 (21 October 2026) while the NeMo Relay matrix still scopes Pi support to 0.84.x, and DeepSeek Harness now publishes two prerelease lines at once - a release-candidate line on 0.2.1 reaching dsh-v0.2.1-rc.5 on 30 October and the newer alpha line dsh-v0.2.2-alpha.2 of 28 October. Nothing else moved: UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post4 with 102 executable checks, the released backend set is still 30 offered bases, and gateway/app.py still sets UHP_VERSION = 2026-09-28.</description>
</item>
<item>
    <title>The reference implementation publishes its own security review, and prepares for an opt-in scan</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-11-01-community-edition-security-review</guid>
    <pubDate>Sun, 01 Nov 2026 05:32:00 +0000</pubDate>
    <description>HarnessRouter stable is unchanged at v0.37.13 from 558a8bbbd548, and development main is now one commit ahead of that tag, e94398d9c91a, merged 31 October 2026 as PR #617. That commit adds a Community Edition security review, a threat model for the self-hosted product, together with the files that prepare the project for an opt-in open-source vulnerability scanning program. The threat model scopes the public code - gateway, runner, ui, protocol and their adapters - as the self-hosted Community Edition, and excludes hosted services, real provider accounts, other people's deployments and third-party agent CLIs and SDKs, while keeping integration mistakes in the project's own code in scope. It describes the one-container layout it assumes: the console publishes only port 3000, the gateway and runner listen on loopback, the runner runs as root only so each agent session runs as its own uid, and the runner's environment carries neither the login nor the secret-store key. The repository states plainly that committing these files does not enroll the project, start a scan, or grant access to a model API; the audit image keeps the full source tree, installs dependencies at build time and builds the self-hosted UI, but does not start the application or authenticate to providers, and the offline check runs the repository's own suites with --network none, reporting 170 passing tests - gateway 11, runner 1, protocol 158 - while noting that a green run means a patch can be tested offline in the image, not that the code is secure. The accompanying workflow validates the payload and runs that check on main and weekly; it checks the environment only and does not submit an enrollment or invoke a model scan. The project is not enrolled and no scan has run. Everything else is unchanged: UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post4 with 102 executable checks = 41 Core, 9 Extended, 52 Full, the released backend set is still 30 offered bases with 30 entries in the runner BACKENDS registry, and gateway/app.py still sets UHP_VERSION = 2026-09-28. This run's rotation was security and evaluation. The IETF identity, enrollment and assurance drafts the security guide tracks could not be re-verified, because the IETF Datatracker, its static archive and the mail archive all answer a Cloudflare challenge to this sandbox; their recorded revisions are left as they were and the gap is reported rather than filled by inference. The weekly competitive cohort was visited for ISO week 44 on 26 October and 1 November is the last day of that week, so it was not yet due.</description>
</item>
<item>
    <title>HarnessRouter v0.37.13, and MCP Server Cards' charter is final</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-31-v0.37.13-server-card-charter</guid>
    <pubDate>Sat, 31 Oct 2026 06:02:00 +0000</pubDate>
    <description>HarnessRouter stable is now v0.37.13 from 558a8bbbd548, published 31 Oct at 04:38:37 UTC. The release renames the starter kit formerly called My Workplace to Harness Bot, and lets a renamed kit keep what was launched under its old name: kit.json can now declare aliases, harness.replaces_packages and harness.replaces_names, and the server reads them, so a setup launched under an old kit id belongs to the kit and the current package takes an old package's place on the next launch instead of being installed beside it. Nothing else moved: the released backend set is still 30 offered bases with 30 entries in the runner BACKENDS registry, the conformance package is still 2026.10.19.post4 with 102 executable checks = 41 Core, 9 Extended, 52 Full, UHP is still 2026-10-19 Draft, and gateway/app.py still sets UHP_VERSION = 2026-09-28. This run's rotation was discovery and execution, and it corrected a stale maturity claim on two pages: SEP-2127, MCP Server Cards, was merged into the MCP specification repository on 6 October 2026 with status Final, naming the extension identifier io.modelcontextprotocol/server-card and chartering the Server Card Working Group, where /uhp-vs-ard/ and /uhp-vs-mcp/ both still said it remained open and unmerged. The wire format is still maintained in the repository named experimental-ext-server-card, whose README says the work is for prototyping and feedback and is not an accepted or official MCP extension. The same rotation found that the ARD specification's text has advanced past the reviewed v0.91 draft, with PRs 80, 105, 106 and 111 merged between 11 and 25 October 2026, while its version block still reads v0.91 and 26 August 2026: section 3.3 now makes type an open media-type string and lists the recognized types with an IANA note that they are de-facto community standards tracking towards registration, the discovery identifier's URN form makes the namespace optional, and a new informative section 5.5 Observability names federated registries as trust boundaries and states that trace context is operational metadata, not ARD entry data, not a trustManifest claim, not an authorization grant and not a relevance-score input.</description>
</item>
<item>
    <title>HarnessRouter v0.37.12, and a retried harness create no longer makes a second harness</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-30-v0.37.12-harness-create-idempotency</guid>
    <pubDate>Fri, 30 Oct 2026 06:48:00 +0000</pubDate>
    <description>HarnessRouter published two stable releases on the evening of 29 October: v0.37.11 at 17:15:36 UTC and v0.37.12 at 18:50:37 UTC. Stable is v0.37.12 from 5520b956ffc1. v0.37.11 makes POST /v1/harnesses honour an Idempotency-Key, as a task already did: when a create reached the server but its answer was lost, the client could not tell whether the harness existed and its retry made a second one. With a key, a repeat answers with the harness the first request created, the same key with a different request is refused 409 idempotency_key_reused, and once that harness is deleted the key names none. The key is kept for 24 hours in the caller's scope, the server reports the new harness_idempotency capability, and Deploy to Cloud sends a key on each create. v0.37.12 makes a failed turn give the provider's own words when the agent harness could not read the refusal: a Qwen Code turn refused by vLLM 0.10.0 or older failed with only API Error: 400 status code (no body), because Qwen Code reads a refusal's reason only under an error key while those vLLM versions put message at the top level, so the one thing a person could fix - a context window too small for the request - was never shown. The protocol text is in Harnesses 5.1 of UHP 2026-10-19, an addition within that version, and conformance suite 2026.10.19.post4 checks it as F-10: 102 executable checks = 41 Core, 9 Extended, 52 Full. Nothing else moved: the released backend set is still 30 offered bases with 30 entries in the runner BACKENDS registry, and gateway/app.py still sets UHP_VERSION = 2026-09-28. This run's rotation was memory and identity, and it corrected the stable Hermes coordinate on five pages: since v0.21.6 the release tag is the agent version itself, so the current stable is Agent v0.22.5, published 23 October 2026, not v2026.9.24 / v0.21.5.</description>
</item>
<item>
    <title>HarnessRouter v0.37.10, and the ACP adapter's current stable is v2</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-29-v0.37.10-acp-adapter-v2</guid>
    <pubDate>Thu, 29 Oct 2026 05:35:00 +0000</pubDate>
    <description>HarnessRouter published two further stable releases on 28 and 29 October: v0.37.9 at 23:44:34 UTC and v0.37.10 at 00:38:16 UTC. Stable is v0.37.10 from 3fa39ad1947f. v0.37.9 makes a produced file appear as soon as its turn is written and lets Qwen Code work with a model whose window is smaller than the cap Qwen Code picks: Qwen Code puts its own max_tokens on every request, so a self-hosted model served with a smaller window refused every turn, and HarnessRouter now drops that field on Qwen Code's requests as it already does for Kimi Code, OpenHands and Vibe. v0.37.10 gives every setup screen one bar and moves DeepSeek Harness model calls onto the runner's relay, so the provider key no longer enters the driver's process and a refused, dropped or timed-out connection ends the turn with an error instead of a dead connection. The ACP adapter's current stable is codex-acp v2.3.0, not v1.12.0: the line moved to v2.0.0 on 28 September with a breaking change to the AIR tool call contract, and v2.3.0 re-adds ACP v2 support, reports the model of each native subagent session and returns initial ACP v2 session commands. The upstream DeepSeek Harness prerelease is now dsh-v0.2.2-alpha.2, with the ACP mode still being fixed in the v0.2.x line. The ACP protocol's own v1.13.0, published 27 October, changes only unstable and unstable-v2 surfaces, so the stable-v1 surface this site describes is unchanged. Nothing else moved: the released backend set is still 30 offered bases with 30 entries in the runner BACKENDS registry, UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post3 with 101 executable checks = 41 Core, 9 Extended, 51 Full, and gateway/app.py still sets UHP_VERSION = 2026-09-28.</description>
</item>
<item>
    <title>HarnessRouter v0.37.8, and how model coverage is decided per base</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-28-v0.37.8-model-coverage</guid>
    <pubDate>Wed, 28 Oct 2026 05:30:00 +0000</pubDate>
    <description>HarnessRouter published five stable releases on 27 October: v0.37.4 at 05:35:18 UTC, v0.37.5 at 06:10:47 UTC, v0.37.6 at 06:43:39 UTC, v0.37.7 at 08:54:40 UTC and v0.37.8 at 20:24:45 UTC. Stable is v0.37.8 from b2091142cdca. The five releases are almost entirely about the four bases added in v0.37.0. v0.37.4 makes Deep Agents Code default to gpt-6.1-sol like the Responses API bases, while Mistral Vibe, Docker Agent and fast-agent keep gpt-5.4 on the connections that refuse gpt-6.1-sol for a request carrying function tools. v0.37.5 lets fast-agent's image-reading models see images, because the runner now tells it what the turn's model reads instead of letting its own table decide, and fits a conversation's images to what the current model takes. v0.37.6 stops fast-agent giving up on a slow model before HarnessRouter does. v0.37.7 treats Nemotron 3 Super as text-only, sends a Gemini thought signature only to the model that made it, gives DeepSeek Harness the setup's and plugin's skills, and switches off DeepSeek Harness's built-in web search, which calls DeepSeek's own service outside the chosen model connection. v0.37.8 withdraws two harness and model pairs: fast-agent with Gemini 4 Argon on Google's own API, and Docker Agent with Grok 4.20. The reference guide now explains the rule behind those decisions: model coverage is decided per base and per connection, a base offers only the models it was measured to run, and the same model can be offered on one base and withheld on another. Nothing else moved: the released backend set is still 30 offered bases with 30 entries in the runner BACKENDS registry, UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post3 with 101 executable checks = 41 Core, 9 Extended, 51 Full, and gateway/app.py still sets UHP_VERSION = 2026-09-28.</description>
</item>
<item>
    <title>HarnessRouter v0.37.3, and four new harness bases</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-27-v0.37.3-thirty-bases</guid>
    <pubDate>Tue, 27 Oct 2026 05:11:00 +0000</pubDate>
    <description>HarnessRouter published four stable releases on 26 October: v0.37.0 at 05:37:39 UTC, v0.37.1 at 10:59:27 UTC, v0.37.2 at 17:38:34 UTC and v0.37.3 at 23:29:42 UTC. Stable is v0.37.3 from ef9e12e29b61. v0.37.0 adds four harness bases, each measured end to end on every provider before release: Mistral Vibe 3.0.2, Docker Agent 1.152.0, fast-agent 0.10.47 and deepagents-code 0.2.1, the last driven over the Agent Client Protocol. The released backend set moves from 26 to 30, and the runner BACKENDS registry now holds exactly those 30 entries: Gajae-Code, which the previous stable implemented but did not offer, is no longer in the registry, so the registry and the product's default HR_BACKENDS set now agree for the first time. v0.37.1 makes fast-agent and Deep Agents Code show each step as it happens, with fast-agent running over its own ACP server; v0.37.2 withdraws nemotron-3.5-lightning from three of the new bases after it wrote deliverables outside the workspace; v0.37.3 lets fast-agent reach MCP servers whose address does not end in /mcp and stops docker-agent running part of the officecli skill as a command. Nothing else moved: UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post3 with 101 executable checks = 41 Core, 9 Extended, 51 Full, and gateway/app.py still sets UHP_VERSION = 2026-09-28. A same-day correction then aligned the /harnessrouter/ backend-set list with the 30 released bases.</description>
</item>
<item>
    <title>AHP reaches 1.0.0, and two pages that contradicted themselves are corrected</title>
    <link>https://unifiedharnessprotocol.dev/uhp-vs-ahp/</link>
    <guid isPermaLink="false">uph-2026-10-26-ahp-1.0.0-cohort-week-44</guid>
    <pubDate>Sun, 26 Oct 2026 05:14:00 +0000</pubDate>
    <description>Microsoft's Agent Host Protocol published spec/v1.0.0 on 2 October 2026. This site's AHP comparison had not caught up with its own introduction: the frontmatter, lead and opening paragraph already named spec/v1.0.0 released 2 October 2026, but the architectural comparison table still said the published spec was 0.9.0 of 28 August 2026 and that the UHP side was the 2026-08-11 draft, and the Current AHP status section still called AHP pre-1.0. The table now states 1.0.0 and the UHP 2026-10-19 draft the comparison actually uses; the status section states the 1.0.0 SemVer and channel-stability table, adding Canvas as Experimental; and the page records the four further open-source AHP hosts and client tools the upstream repository now lists. The HoH-lite availability claim was wrong twice over: the project README has announced HoH-lite as available since 24 September 2026 and this site's page said so in its current guidance, while Status first still said the repository explicitly says HoH-lite is coming soon and the evidence limits still said it is not yet publicly released. Status first now dates the coming soon wording to the 4 September snapshot, and the evidence limit is restated accurately: HoH-lite is published, but it is a lightweight implementation of the core workflow, and the paper's benchmark and multi-day results still need the benchmark checkout, Node.js/npm, bubblewrap, Xvfb, xdotool and FFmpeg, so they are not reproducible from the packaged runtime alone. Core coordinates are unchanged: HarnessRouter stable v0.36.4, UHP 2026-10-19 Draft, conformance 2026.10.19.post3 with 101 executable checks = 41 Core, 9 Extended, 51 Full, and 26 released backends with 27 entries in the runner BACKENDS registry.</description>
</item>
<item>
    <title>HarnessRouter v0.36.4, and MCP's first agent-discovery draft</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-25-v0.36.4-post3-101</guid>
    <pubDate>Sun, 25 Oct 2026 05:10:00 +0000</pubDate>
    <description>HarnessRouter published two stable releases on 24 and 25 October: v0.36.3 at 06:35:09 UTC and v0.36.4 at 02:42:30 UTC. Stable is v0.36.4 from edca78bffa40. v0.36.3 fixes Deploy to Cloud for a setup's second destination, stores a codex command's output whole, and answers a shared link with 503 when its Task cannot be read; v0.36.4 keeps a setup's open task on screen when the window narrows to a phone, and stops codex's own warnings being listed as tool calls. One protocol-surface fact is worth naming: a function_call_output item now has status: incomplete when the tool's output could not be read in full, instead of completed. The release states this stays within UHP 2026-10-19, because the schema leaves an output item's status an open string and incomplete is the value a response already uses for work that did not finish. The Tasks 3.1 example still shows completed, so a client that assumes every tool output is completed is reading a field the specification does not fix. MCP's Agents Working Group also merged its first concrete agent-facing draft: PR 22 on 20 October adds a Draft Extensions Track proposal with the proposed identifier io.modelcontextprotocol/agents, a two-stage flow in which a host reads a compact roster of agent names and capability labels and then the instructions and scoped tool schemas for the agent it selected. Nothing else moved: UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post3 with 101 executable checks = 41 Core, 9 Extended, 51 Full, and the released backend set is still 26 offered bases with 27 entries in the runner BACKENDS registry.</description>
</item>
<item>
    <title>HarnessRouter v0.36.2, and the first optional UHP capability the reference implementation advertises</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-24-v0.36.2-input-history</guid>
    <pubDate>Fri, 24 Oct 2026 05:10:00 +0000</pubDate>
    <description>HarnessRouter published three stable releases on 23 October: v0.36.0 at 09:27:53 UTC, v0.36.1 at 19:57:09 UTC and v0.36.2 at 21:38:52 UTC. Stable is v0.36.2 from 66eb6e55f956. v0.36.0 is a minor release: it brings the redesigned console to self-hosted instances, with Start, Studio, Shop, Add-ons, API Keys, Bring your own key, Profile and Workspaces, the old addresses redirecting, and a setup deployable to HarnessRouter Cloud from one button. The protocol-facing change is the optional input_history capability: POST /v1/responses can bring a task's earlier turns, with the messages before the last user message becoming the task's first turn, marked imported, with no model and no cost, and UHP_CAPABILITIES in gateway/app.py now carries input_history: true with the source comment citing Tasks 2.1. That is the first optional capability from UHP 2026-10-19 the reference implementation has advertised. No conformance check exercises it, so a conformance report cannot establish it; a client reads it from GET /v1/uhp. Nothing else moved: UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post3 with 101 executable checks = 41 Core, 9 Extended, 51 Full, the released backend set is still 26 offered bases with 27 entries in the runner BACKENDS registry, and gateway/app.py still sets UHP_VERSION = 2026-09-28.</description>
</item>
<item>
    <title>HarnessRouter v0.35.17, four stable releases on 22 October, conformance unchanged at 101 checks</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-23-v0.35.17-post3-101</guid>
    <pubDate>Fri, 23 Oct 2026 05:15:00 +0000</pubDate>
    <description>HarnessRouter published four stable releases on 22 October between 05:35 and 09:58 UTC: v0.35.14, v0.35.15, v0.35.16 and v0.35.17. Stable is v0.35.17 from 7f036edf545b. The four releases share one theme: a read that could not be made whole is reported instead of being answered from what happened to be there, so a failed canvas read never wipes a video, a transcript is never shown with a hole in it, an unreadable response answers 503 to try again instead of a permanent response_not_found, a download of files that cannot be made whole answers file_not_found, and the storage total is never a false zero. v0.35.14 also makes gpt-6.1-sol the default model where gpt-5.4 was, on the ten harnesses where it passed every check on the OpenAI, Azure and TokenRouter connections, and makes a failed task name the harness and the tool that failed; v0.35.16 refines conformance check R-07 and makes a missing schema validator its own condition; v0.35.17 gives a failed Agent Zero turn the same stack trace every other harness already had. Nothing else moved: UHP is still 2026-10-19 Draft, the conformance package is still 2026.10.19.post3 with 101 executable checks = 41 Core, 9 Extended, 51 Full, and the released backend set is still 26 offered bases with 27 entries in the runner BACKENDS registry. v0.36.0-rc.1 through rc.4 are release candidates, so no coordinate changes on their account.</description>
</item>
<item>
    <title>Conformance check T-12 corrected: a Full check on the step budget, not a Core check on the timeout path</title>
    <link>https://unifiedharnessprotocol.dev/conformance/</link>
    <guid isPermaLink="false">uph-2026-10-22-t12-step-budget-correction</guid>
    <pubDate>Thu, 22 Oct 2026 05:30:00 +0000</pubDate>
    <description>The 21 October description of conformance check T-12 was wrong in two ways, and is corrected here and on the conformance, lifecycle and news pages. T-12 is a Full check, not a Core check, and it constrains the step budget, not the timeout path: it sends max_step: 1 for work that needs three tool-call rounds and requires the task to end incomplete and name the budget that stopped it, while a server that cannot bound its base names max_step in metadata.ignored_fields and passes. No check in the suite exercises the timeout_seconds wall-clock budget. The registry is unchanged at 101 executable checks = 41 Core, 9 Extended, 51 Full for package 2026.10.19.post3. The security and lifecycle pages also carried a stale normative version label and are now stated at 2026-10-19, and the security page's primary-source links are relabelled to the revision they actually serve. Core coordinates re-verified on 22 October 2026 and unchanged: UHP 2026-10-19 Draft, HarnessRouter stable v0.35.13 from 3668370c1025, 26 released backends.</description>
</item>
<item>
    <title>HarnessRouter v0.35.13, three releases in one day, conformance 2026.10.19.post3 (101 checks)</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-21-v0.35.13-post3-101</guid>
    <pubDate>Wed, 21 Oct 2026 14:30:00 +0000</pubDate>
    <description>HarnessRouter shipped v0.35.11, v0.35.12 and v0.35.13 between 03:12 and 08:10 UTC; stable is v0.35.13 from 3668370c1025. v0.35.11 makes interrupted work say so: a task cut short by a server restart or a gateway shutdown ends failed with detail.reason interrupted, and on self-hosted installs the files an interrupted task wrote survive a recreated container because the checkpoint markers moved to the data volume. v0.35.12 ends a task that is still waiting when the hard time limit passes with reason timeout in its response record, so a client polling GET /v1/responses/{id} sees the end, and such a task never starts its agent afterwards. v0.35.13 answers 503 with type server_error when the server cannot read a stored conversation, instead of a 200 with the unreadable turns left out. The conformance suite is 2026.10.19.post3 with 101 executable checks = 41 Core, 9 Extended, 51 Full; post3 added T-12, which measures the step budget. Released backend count remains 26, and the runner BACKENDS registry still holds 27 entries; no server advertises memories, harness_retirement or input_history yet.</description>
  </item>
  <item>
    <title>HarnessRouter v0.35.10, four releases in one day, conformance 2026.10.19.post2 (100 checks)</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-20-v0.35.10-post2-100</guid>
    <pubDate>Mon, 20 Oct 2026 01:30:00 +0000</pubDate>
    <description>HarnessRouter shipped v0.35.7 through v0.35.10 between 07:01 and 00:48 UTC; stable is v0.35.10 from caa3c0a1. v0.35.7 carries the remaining UHP 2026-10-19 additions into the product: input_history (Tasks 2.1), per-turn created_at/completed_at (Sessions 3), and background responses answering in_progress rather than an implementation's own name for the state; an idempotent replay whose original response is gone now answers 404 response_not_found, the produced-file attachment cap is 64 MiB, and a cancel answered cancelled now holds. v0.35.8 deprecates the harness models view's fallback field (removed no earlier than the second version after 2026-10-19). The conformance suite is 2026.10.19.post2 with 100 executable checks = 41 Core, 9 Extended, 50 Full; post1 added T-11 (a background read mid-turn reports in_progress). Released backend count remains 26; no server advertises memories, harness_retirement or input_history yet.</description>
  </item>
<item><title>UHP 2026-10-04 adds the optional Memories chapter, and HarnessRouter v0.35.1 ships</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-2026-10-04-memories-harnessrouter-v0.35.1-2026-10-18</guid><pubDate>Sat, 18 Oct 2026 08:40:00 GMT</pubDate><description>UHP 2026-10-04 is additive to 2026-09-28 and adds one chapter, Memories: a tree of memories with access granted per node, records, recall, providers, and the four moments a harness reaches memory. The conformance package is 2026.10.4.post11 with 98 executable checks, 40 Core, 9 Extended and 49 Full, including 13 memories checks. HarnessRouter Community Edition stable is v0.35.1, published 18 October 2026 at 06:26:23 UTC, and the released backend set is 26 after v0.33.0 added MiMo Code, jcode, OpenSquilla, nanobot and Qoder Cloud Agent. Community Edition still advertises UHP 2026-09-28, so the optional memories capability is not established in that implementation.</description></item>

<item><title>Developer guide: a reading path for every execution boundary</title><link>https://unifiedharnessprotocol.dev/</link><guid isPermaLink="false">uhp-guide-refinement-v2-2026-10-04</guid><pubDate>Sun, 04 Oct 2026 12:29:22 GMT</pubDate><description>The independent guide adds substantive task and decision guidance across its 109 routes, organizes the reference into seven reader-oriented subject groups, and provides a local interface chooser. Source reviews distinguish stable releases, development revisions and historical evidence; unavailable current normative detail remains explicitly unresolved.</description></item>
<item><title>Developer guide: practical integration paths and clearer evidence</title><link>https://unifiedharnessprotocol.dev/</link><guid isPermaLink="false">uhp-guide-overhaul-2026-10-04</guid><pubDate>Sun, 04 Oct 2026 09:38:57 GMT</pubDate><description>The independent guide now separates current setup advice from historical release evidence, adds task-focused entry paths, improves keyboard-accessible reference tables and distinguishes protocol versions, software releases and conformance measurements. Qwen Live, NeMo Relay and protocol comparisons have refreshed practical guidance.</description></item>
<item><title>HarnessRouter v0.29.1 fixes relay streaming and upstream liveness</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.29.1-2026-10-04</guid><pubDate>Sun, 04 Oct 2026 15:17:35 GMT</pubDate><description>HarnessRouter v0.29.1 forwards provider streams as data arrives, makes event-level upstream silence time out even when keep-alive lines continue, applies the same relay liveness rules to DeepSeek Harness, and fixes RC publication semantics. UHP remains 2026-09-28, conformance remains 2026.9.28.post3 with 85 executable checks, and the released backend count remains 20.</description></item>
  <item><title>HarnessRouter v0.29.0 adds four new harness bases</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.29.0-2026-10-04</guid><pubDate>Sun, 04 Oct 2026 00:33:05 GMT</pubDate><description>HarnessRouter v0.29.0 adds Kilo CLI, MiniMax Code, Grok Build and Agent Zero, taking the released backend set from 16 to 20, together with relay and secret-handling hardening. UHP remains 2026-09-28 and conformance remains 2026.9.28.post3 with 85 executable checks.</description></item>
<item><title>Oh My Pi v18.1.19 promotes the tracked reliability line to stable</title><link>https://unifiedharnessprotocol.dev/oh-my-pi/</link><guid isPermaLink="false">uhp-news-oh-my-pi-v18.1.19-2026-09-12</guid><pubDate>Sat, 12 Sep 2026 23:57:09 GMT</pubDate><description>Oh My Pi v18.1.19 promotes the tracked MCP reconnect, DeepSeek V4.1 Flash, replay-safe retry, per-fallback reasoning effort, persistent context-isolated /btw and JSON print-mode exit-status work into stable behavior and adds live-tool, provider-auth and Windows reliability fixes. HarnessRouter v0.16.1 still measures OMP 18.1.13; upstream latest and adapter evidence remain separate coordinates.</description></item>
<item><title>UHP 2026-09-12 adds the optional Harness Plugins sub-protocol</title><link>https://unifiedharnessprotocol.dev/harness-plugins/</link><guid isPermaLink="false">uhp-news-2026-09-12-harness-plugins</guid><pubDate>Sat, 12 Sep 2026 23:40:40 GMT</pubDate><description>UHP 2026-09-12 adds optional Harness Plugins using Agent Plugins 1.0.0 as the package format and advances the conformance package to 2026.9.12 with 74 checks. The checked-in HarnessRouter reference result remains the prior-suite 64/64 Full run; PR #165 says Community Edition still reports plugins unsupported at that merge point, so no 74/74 runtime result is claimed.</description></item>
<item><title>HarnessRouter v0.16.1 adds explicit custom-endpoint model maps and connection tool policy</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.16.1-custom-endpoint-controls-2026-09-11</guid><pubDate>Fri, 11 Sep 2026 07:28:18 GMT</pubDate><description>HarnessRouter v0.16.1 releases PR #155: custom endpoint model rows become explicit per-connection canonical-to-wire mappings, custom endpoints gain OpenAI Responses format, connection-level disabled tools are applied per turn, and Codex is pinned to 0.154.0. UHP remains 2026-08-11, the backend set remains ten and conformance remains 64 checks.</description></item>
<item><title>HarnessRouter v0.16.0 adds hosted HarnessRouter as an optional Community Edition provider</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.16.0-hosted-provider-2026-09-11</guid><pubDate>Fri, 11 Sep 2026 04:52:35 GMT</pubDate><description>HarnessRouter v0.16.0 releases PR #151 and lets self-hosted Community Edition pair with HarnessRouter API as an optional provider through a server-mediated key hand-off. The gateway keeps pairing and provider credentials server-side, stores the hosted endpoint and model-catalog coordinates, and preserves hosted routing for Gemini. UHP remains 2026-08-11, the backend set remains ten, and conformance remains 64 checks.</description></item>
<item><title>HarnessRouter v0.15.10 defaults Codex to app-server and makes provider-history refusal explicit</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.15.10-codex-app-server-2026-09-10</guid><pubDate>Thu, 10 Sep 2026 09:07:08 GMT</pubDate><description>HarnessRouter v0.15.8-v0.15.10 normalize Codex app-server item spelling, make app-server the default execution path with an explicit codex-exec rollback, and turn cross-route encrypted-reasoning continuation refusal into an actionable provider error. Post-release PR #148 reruns the Codex provider columns on the app-server path and records 43/44 Vercel, 43/44 TokenRouter, 44/44 OpenAI, 44/44 Azure and 43/44 OpenRouter. These are HarnessRouter runtime/provider compatibility results, not UHP conformance.</description></item>
<item><title>HarnessRouter v0.15.7 makes lost resumes explicit and fixes Hermes Azure API-mode selection</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.15.7-resume-hermes-azure-2026-09-08</guid><pubDate>Tue, 08 Sep 2026 19:31:35 GMT</pubDate><description>HarnessRouter v0.15.7 releases PR #139. Later GPT-family models such as gpt-6-astra on Azure Foundry are routed through Hermes Responses mode, while missing Claude Code or OpenCode native sessions emit an explicit lost-resume signal and fail the support-matrix recall verdict instead of passing as fresh continuity. UHP remains 2026-08-11, conformance remains 64 checks and the released backend set remains ten.</description></item>
<item><title>HarnessRouter v0.15.6 closes the custom-harness MCP verification gap</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.15.6-dsh-mcp-verification-2026-09-08</guid><pubDate>Tue, 08 Sep 2026 13:31:18 GMT</pubDate><description>HarnessRouter v0.15.6 releases runtime and verification hardening from PRs #135-#138. The DeepSeek Harness adapter moves to 0.1.2rc1 with configured MCP-server driving, Oh My Pi tool/MCP metadata is corrected, runnable-model availability requires server evidence, and the custom-harness verification dimension now exercises a real MCP server across all ten built-in harness bases when its external endpoint is reachable. UHP remains 2026-08-11 and conformance remains 64 checks.</description></item>
<item><title>HarnessRouter v0.15.5 is stable; current main codifies stronger verification rules</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.15.5-verification-methodology-2026-09-08</guid><pubDate>Tue, 08 Sep 2026 06:35:08 GMT</pubDate><description>HarnessRouter v0.15.5 is the latest stable release at that cutoff. v0.15.4-v0.15.5 refine README and Quickstart presentation without changing UHP, provider routing, ten-backend state or conformance. PR #133 adds explicit support-matrix and custom-harness verdict methodology; v0.15.6 later extends that implementation-level dimension to an MCP server.</description></item>
<item><title>HarnessRouter v0.15.3 hardens hosted login-state cookies</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.15.3-hosted-login-cookies-2026-09-08</guid><pubDate>Tue, 08 Sep 2026 01:31:06 GMT</pubDate><description>HarnessRouter v0.15.3 releases hosted/shared-console authentication hardening from PRs #125 and #127: the bearer cookie is host-only, HttpOnly, Secure and SameSite=Lax; login cookies are reconciled from the current session and migration can validate either of two same-name cookies. The paths are explicitly inert self-hosted. UHP remains 2026-08-11, conformance remains 64 checks and the released backend set remains ten.</description></item>
<item><title>HarnessRouter v0.15.2 documents ten harnesses and strengthens artifact-card evidence</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.15.2-ten-harnesses-artifact-evidence-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 23:09:55 GMT</pubDate><description>HarnessRouter v0.15.2 releases PRs #121-#123: artifact evidence now distinguishes rendered file-card count from older filename-only checks, README imagery reflects ten built-in harnesses, and gpt-6-astra is added on compatible routed provider/backend paths. UHP remains 2026-08-11 and conformance remains 64 checks.</description></item>
<item><title>HarnessRouter v0.15.1 fixes the console send latch and duplicate file cards</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.15.1-send-latch-file-card-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 21:27:13 GMT</pubDate><description>HarnessRouter v0.15.1 releases PR #120. A turn settling outside the POST stream no longer leaves later sends silently rejected, and the same produced file is de-duplicated when it arrives through both the POST stream and a late live-forward broadcast.</description></item>
<item><title>Oh My Pi becomes HarnessRouter's tenth released backend in v0.15.0</title><link>https://unifiedharnessprotocol.dev/oh-my-pi/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.15.0-oh-my-pi-backend-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 17:43:08 GMT</pubDate><description>HarnessRouter v0.15.0 releases PR #68 and adds Oh My Pi as the tenth built-in harness backend. PR #119 separately records 705/705 OMP scenario runs across seven provider columns using Oh My Pi 18.1.13 under its stated pre-release conditions. This is HarnessRouter adapter evidence, not native Oh My Pi UHP adoption.</description></item>
<item><title>HarnessRouter v0.14.5 makes deleted tasks final and pins every Gemini helper alias</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.14.5-deleted-task-gemini-helpers-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 05:31:43 GMT</pubDate><description>HarnessRouter v0.14.5 releases PR #117. Deleted and unknown session IDs are refused before work runs, owned tombstones can be deleted idempotently, continuation-read 503 failures use the protocol-defined server_error code, and all eighteen model-naming Gemini CLI 0.58.0 helper aliases are pinned to the turn model. UHP remains 2026-08-11 and conformance remains 64 checks.</description></item>
<item><title>HarnessRouter v0.14.4 pins Gemini CLI helper calls to the turn model</title><link>https://unifiedharnessprotocol.dev/gemini-cli/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.14.4-gemini-helper-model-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 04:48:00 GMT</pubDate><description>HarnessRouter v0.14.4 releases PR #116 after Gemini CLI housekeeping calls were observed using helper tiers that appeared as a second model in turn statistics. HarnessRouter pins those tiers to the turn model, carries the canonical model ID, and reports the runner error before result text on failure.</description></item>
<item><title>HarnessRouter v0.14.3 adds TokenRouter's native Google path for Gemini CLI</title><link>https://unifiedharnessprotocol.dev/gemini-cli/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.14.3-gemini-tokenrouter-native-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 04:39:37 GMT</pubDate><description>HarnessRouter v0.14.3 releases PR #115. TokenRouter can serve the Gemini CLI backend through Google's native v1beta generate and stream API shape while preserving the vendor-table model identity and requested-versus-served checks.</description></item>
<item><title>HarnessRouter v0.14.2 prevents silent Gemini CLI model fallback</title><link>https://unifiedharnessprotocol.dev/gemini-cli/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.14.2-gemini-fallback-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 02:53:38 GMT</pubDate><description>HarnessRouter v0.14.2 releases PR #114. Each resolvable Gemini candidate chain now contains only the requested model, so provider retries stay on that model and provider failure ends the turn instead of silently falling back. Failed-turn reasons are kept separate from finished answer text. UHP remains 2026-08-11 and conformance remains 64 checks with the checked-in 64/64 Full reference result.</description></item>
<item><title>HarnessRouter v0.14.1 changes the Gemini default to gemini-3.8-flash</title><link>https://unifiedharnessprotocol.dev/gemini-cli/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.14.1-gemini-default-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 02:43:47 GMT</pubDate><description>HarnessRouter v0.14.1 releases PR #113, adding the Gemini harness mark and changing the HarnessRouter Gemini default to gemini-3.8-flash across the catalogue, runner and console placeholder. This is a HarnessRouter product default, not a UHP protocol default.</description></item>
<item><title>HarnessRouter v0.14.0 makes Gemini model identity enforceable</title><link>https://unifiedharnessprotocol.dev/gemini-cli/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.14.0-gemini-identity-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 00:44:54 GMT</pubDate><description>HarnessRouter v0.14.0 releases PR #111. The measured Gemini model identifiers are configured to serve as themselves, and a requested/observed serving-model mismatch fails instead of being counted as a successful compatibility turn. The PR records 11 measured Gemini IDs. UHP remains 2026-08-11 and conformance remains 64 checks with the checked-in 64/64 Full reference result.</description></item>
<item><title>Gemini CLI becomes HarnessRouter's ninth released backend</title><link>https://unifiedharnessprotocol.dev/gemini-cli/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.13.24-gemini-backend-2026-09-06</guid><pubDate>Sun, 06 Sep 2026 23:16:54 GMT</pubDate><description>HarnessRouter v0.13.24 releases PR #72 and adds Gemini CLI as the ninth backend. HarnessRouter pins Gemini CLI 0.58.0 for the adapter, drives its stream-JSON mode and uses the direct Google API-key integration path. This is HarnessRouter adapter support, not native Google UHP adoption.</description></item>
<item><title>HarnessRouter v0.13.25-v0.13.26 expand Gemini matrix coverage and restore retry</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.13.25-v0.13.26-2026-09-07</guid><pubDate>Mon, 07 Sep 2026 00:17:37 GMT</pubDate><description>v0.13.25 adds Gemini-family/provider support-matrix coverage and provider-aware backend integration selection through PRs #106 and #109. v0.13.26 releases PR #110, retrying a refused workspace restore for roughly 90 seconds and naming the refusal cause while retaining fail-closed behavior.</description></item>
<item><title>HarnessRouter main publishes the self-hosted support matrix after v0.13.13</title><link>https://unifiedharnessprotocol.dev/harnessrouter/</link><guid isPermaLink="false">uhp-news-harnessrouter-support-matrix-pr93-2026-09-06</guid><pubDate>Sun, 06 Sep 2026 16:33:39 GMT</pubDate><description>HarnessRouter PR #93 publishes 695 harness-model pairs across eight provider columns, five scenarios per eligible pair and a separate 35-minute cold-recall probe across the eight then-released backends. This matrix predates the Gemini CLI backend and remains point-in-time HarnessRouter implementation evidence, not UHP conformance.</description></item>
<item><title>HarnessRouter v0.13.11-v0.13.13 harden routing and checkpoint recovery</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.13.11-v0.13.13-2026-09-06</guid><pubDate>Sun, 06 Sep 2026 14:05:22 GMT</pubDate><description>HarnessRouter v0.13.11 through v0.13.13 harden direct-key Claude base normalization, provider-column support-matrix fidelity, fail-closed checkpoint restore and owner-trust Azure provider-base normalization. UHP remains 2026-08-11 and conformance remains 64 checks.</description></item>
<item><title>HarnessRouter v0.13.10 releases relay version-path fix</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.13.10-2026-09-06</guid><pubDate>Sun, 06 Sep 2026 10:23:14 GMT</pubDate><description>HarnessRouter v0.13.10 releases PR #86, adding an API-version path when the loopback relay receives a provider base without one. The change fixes direct-Anthropic Cline first turns and Qwen tool turns that had reached unversioned routes and returned 404 while preserving already-versioned and AWS-specific paths.</description></item>
<item><title>HarnessRouter v0.13.5 adds Google AI Studio provider routing</title><link>https://unifiedharnessprotocol.dev/releases/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.13.5-google-ai-studio-2026-09-06</guid><pubDate>Sun, 06 Sep 2026 02:16:47 GMT</pubDate><description>HarnessRouter v0.13.5 releases Google AI Studio as provider routing for Hermes, Pi, DeepSeek Harness, OpenCode, Qwen Code and Cline through Gemini's OpenAI-compatible endpoint. This provider path is separate from the dedicated Gemini CLI backend that later ships in v0.13.24.</description></item>
<item><title>HarnessRouter v0.13.3 publishes checked-in 64/64 UHP Full reference evidence</title><link>https://unifiedharnessprotocol.dev/conformance/</link><guid isPermaLink="false">uhp-news-harnessrouter-v0.13.3-64-of-64-2026-09-05</guid><pubDate>Sat, 05 Sep 2026 00:21:52 GMT</pubDate><description>PR #64 incorporates the live 4 September 64/64 Full, zero-fail/skip/error HarnessRouter reference measurement into current protocol/conformance source. UHP remains 2026-08-11 and the suite remains 64 checks.</description></item>
  <item>
    <title>UHP 2026-10-19, HarnessRouter v0.35.6, conformance 2026.10.19 (99 checks)</title>
    <link>https://unifiedharnessprotocol.dev/releases/</link>
    <guid isPermaLink="false">uph-2026-10-19-v0.35.6-2026.10.19</guid>
    <pubDate>Sun, 19 Oct 2026 00:00:00 +0000</pubDate>
    <description>UHP moves to 2026-10-19 (additive to 2026-10-04; one rule changes — the harness_retirement capability — the rest is additive). Conformance package moves to 2026.10.19 with 99 executable checks (40 Core, 9 Extended, 50 Full), including the 13 ME- Memories checks and the new F-09 retirement check. HarnessRouter stable is v0.35.6 (28cac79a, 19 Oct 2026 at 03:48:00 UTC). The release line between the two stables includes v0.35.2, v0.35.3, v0.35.4, v0.35.5 and v0.35.6. Released backend count remains 26; the runner BACKENDS registry holds 27, the extra being Gajae-Code (implemented in the runner and deliberately not offered). Development main was separately observed at 9ecd0046 on 19 October 2026 and still advertises UHP 2026-09-28 in gateway/app.py; no server advertises the new capabilities.</description>
  </item>
</channel>
</rss>
