News for hackers. Stuff that matters.

kuanzema

Re:Alibaba's Qoder Adopts the Unified Harness Protocol (UHP) on Thursday October 15, 2026 @02:04PM (#50107641)
HarnessRouter Cloud to directly test it out: https://harnessrouter.ai/
Re:Alibaba's Qoder Adopts the Unified Harness Protocol (UHP) on Thursday October 15, 2026 @02:02PM (#50107624)
Open-source repo to check out the integration: https://github.com/HarnessRouter/harnessrouter
Re:Alibaba's Qoder Adopts the Unified Harness Protocol (UHP) on Thursday October 15, 2026 @01:57PM (#50107539)
Co-founder of HarnessRouter here. Proud to welcome Qoder to the ecosystem.

What we find great about this integration is that one more great agent harness is now available to developers: not as a coding tool, but as an entire plug-and-play backend harness.

Traditionally, building an agent product means building the entire agent harness system, either entirely from scratch or using frameworks such as LangChain and LangGraph.

We see that today, the harness layer could be commoditized as more harnesses are built and shipped by frontier labs and big tech companies.

We've seen developers building video editing products with Hermes as their backend, building compliance document review apps with Claude Code as their backend, building shopping agents with harnesses with agent cart, and building VC scout agents with browser use tools added to the DeepSeek harness. Now, we are looking forward to seeing what developers can build with Qoder as their agent backend harness.

Questions for the community: Which harness would you like to see adopt UHP next? What would you build with a complete, out-of-the-box agent harness?

We built SOH because system one models need a different runtime than system two models.

After building and running SOH, I'm thinking that we might only need different types of system one models and System One Harness to process many types of work, with system two harnesses handling planning, in-the-loop key decisions, and final review. That could be more efficient and effective than training one model to do everything.

Think of it as a reflex-and-brain split: the system two harness and model work like the brain, while System One Harness (SOH) and system one models work like reflexes, handling the majority of jobs without deliberation, and the brain only jumps in when something is uncertain or fails.

What I'd like to learn from the community: what use cases would you like to see from System One Harness, and how would you integrate SOH with a system two harness? Where do you see the reflex-and-brain split breaking?

On top of that, in HarnessRouter cloud: we provide developers with seamless deployment for their serveless, managed agents in sandboxes that can scale at anytime; and tracing insights so they can pick the best Harness × Model × Tools × Skills combination based on production performance. In one benchmark, one combination is 99.8% cheaper, and one combination is 3.2× faster. Check out the benchmark here: https://harnessrouter.ai/benchmarks
Here's Kuanze, co-founder of HarnessRouter. Before building HarnessRouter, I was building an entire harness to power other products. Building a harness was pretty fun for me. I enjoyed and learned quite a lot through building it.

However, Richard asked me a question: how do you plan to keep up with the iteration speed of harnesses like Codex and Claude code. That question leads to the solution that we are delivering to the community today.

From our perspective, the agent harness is becoming an independent infra layer, and it should become a dev tool. Our goal is to make agent harnesses plug-and-play solution for all developers, so they can skip rebuilding the infra layer and focus on shipping product features.

We welcome all comments, feedbacks, protocol contributions, and feature suggestions.

Re:qm on Sunday August 02, 2026 @09:38PM (#49150270)
How is QM trying to differentiate from HarnessRouter.ai, which launched on Launch YC about 10 days ago? https://www.ycombinator.com/launches/RpL-harnessrouter-bring...

Both seem to provide a unified interface across different harnesses/models. HarnessRouter exposes that as a developer API for embedding agent-powered features into products, with Task / Run / Session / Streaming / File / Artifact / Renderer contracts, plus tracing around harness/model behavior over time.

Is the main distinction that QM is a company workspace, while HarnessRouter is an embeddable harness layer for product teams and enterprises?