Evidence record / openhands
A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.
2026-09-21-openhands-acp-harness-surfacing-becomes-an-explicit-per-harness-decision-the-acp-registry-pin-now
ACP harness surfacing becomes an explicit per-harness decision; the ACP registry pin now follows the agent server. #17228: SDK 1.45.0 registered new ACP harnesses (kimi-code, pi, opencode). Canvas’s credential form read the SDK registry directly, so it offered credential fields for harnesses Canvas never listed. Canvas now has one surfaced list, and a test fails if a surfaced harness disappears upstream. #17423: the UI’s ACP registry (npm @openhands/typescript-client 1.39.0) had drifted seven minors behind the agent server that launches the adapters. The pins are now tied together and CI checks them. The Codex shim for GPT-6 Astra (#17164) is gone.
Channel: tagged-release. Half: both. Date: 2026-09-11 (v1.18.0), 2026-09-16 (v1.19.0).
Operator consequence: On v1.19.0 and later, the harness picker matches what the pinned agent server can launch. On earlier tags, do not enter credentials for a harness that shows up only in the credential form.
Receipt
Finding metadata
Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0
Finding ID: 2026-09-21-openhands-acp-harness-surfacing-becomes-an-explicit-per-harness-decision-the-acp-registry-pin-now
Profile citations
- OpenHands / claim / acp-harness-list-explicit
Source links
Primary links, including exact changelog lines when available.
- merged pr2026-09-21-openhands-acp-harness-surfacing-becomes-an-explicit-per-harness-decision-the-acp-registry-pin-nowgithub.com/OpenHands/OpenHands/pull/17228merged pr2026-09-21-openhands-acp-harness-surfacing-becomes-an-explicit-per-harness-decision-the-acp-registry-pin-nowgithub.com/OpenHands/OpenHands/pull/17423
Versioned source: run artifact