UHP统一Harness协议与HarnessRouter开源实现

Big release here! After MCP, A2A, & AG-UI, there's another agent protocol: And this one is built for Agent harnesses: UHP (Unified Harness Protocol) is a standardized interface for running agent tasks across any agent harness, regardless of which one you use. HarnessRouter is its open-source server implementation. Here's how it works: - Your product backend sends a task + harness_id to HarnessRouter. - HarnessRouter routes it to whichever configured harness should run it. - The harness streams progress and artifacts back through HarnessRouter. - HarnessRouter returns the output to your product. Three core components handle this: - Gateway: Responses API, harness config, your model keys. - Runner: Isolated workspaces, one event stream, turn checkpoints. - Built-in tools: MCP servers, browser, database, GitHub, media. This means your agent infra becomes fully interchangeable. - Swap Codex for Claude Code without touching your product code. - Run the same task across different harnesses and compare outputs. - Add new harnesses as they emerge without any rewrites. Here's the repo: https://t.co/4y6zJShKSu (don't forget to star it ⭐) The savings can be substantial. In HarnessRouter's first controlled benchmark, changing only the harness reduced cost by up to 2.1×, with the cheaper setup using roughly 53% fewer credits on the same model. And Alibaba Cloud's Qoder has already officially adopted UHP, making it available as an agent backend through the HarnessRouter API. If you want to dive deeper, my co-founder's recent article explains why model routing is not the same as harness routing, and what it takes to support multiple harnesses. It also covers UHP, the full local setup, a working API call, and how sessions and files work. Read it below.

https://t.co/MNpA3r6Mc7