Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

HarnessRouter: Unified interface for agent harnesses

Details

External ID
49335595
Source
HN
Company
—
Product
HarnessRouter: Unified interface for agent harnesses
Website domain
github.com
Launched
Aug. 17, 2026
Cohort
—
Upvotes
10
Upvotes percentile
0.5772849462365591
Tags
—
Fetched at
Sept. 10, 2026, 5:32 a.m.
Updated at
Sept. 10, 2026, 5:32 a.m.

Description

Hey HN! We are building HarnessRouter, a canonical API for running Codex, Claude Code, Hermes, and other managed agent harnesses as your product backend.Before building HarnessRouter, I used to build our own agent harness for our products. I tried LangGraph, agent SDKs from different vendors, pydantic, LLM tool use / function call, and so on. It's a very heavy lifting engineering effort, and I am disappointed about the agent deliveries compared to what Codex, CC can deliver. That changed my mindset. The frontier labs and famous open source communities are already putting so much engineering effort to build the world's best harnesses, why not leverage them directly instead of building our own, just like how we call LLM chat completion endpoints instead of training our own models?We provide a docker image to run HarnessRouter locally.----------Quickstart: docker pull harnessrouter/harnessrouter docker run -d --name harnessrouter -p 127.0.0.1:3000:3000 -v harnessrouter:/data harnessrouter/harnessrouter docker logs -f harnessrouter Wait for the "ready on :3000" show up, then open the browser at http://localhost:3000. Default username/password is harnessrouter/harnessrouter Then in Integrations page, add your model provider credentials or API keys. In Harnesses tab, as of today we provide routing to Codex, Claude Code, and Hermes as base harnesses. You can customize any of them and configure harness instruction, MCP tools, and skills. Then go to Tasks and let them do jobs. ----------Every harness has its own request/response format and incompatible with each other. We propose Unified Harness Procotol [1] to standardize how an application talks to an agent harness. It covers harness selection and configuration, task execution, event streaming, sessions start cancel and resume, artifact management and delivery, and failure handling. It's similar idea like LiteLLM, but for harnesses rather than models.HarnessRouter implements UHP. We provide an AGENTS.md [2] and your coding agent can follow it to integrate your application with the harnesses available.We also provide starter kits [3] to demonstrate some types of agentic products that can be built on HarnessRouter. It currently includes PPT agent, Spreadsheet agent, BI Dashboard agent, and Video generation agent.Can't wait to hear what you think![1] https://unifiedharnessprotocol.org[2] https://harnessrouter.ai/agents.md[3] https://github.com/harnessrouter/starter-kit

Enrichment

Theme
AI agent frameworks and developer tools
Vertical
Horizontal
Function
Agent / copilot
Audience
Developer
AI stance
AI feature
Project type
Commercial product
Normalized one-liner
unified interface for agent harnesses
Manually corrected
False

Could you build this?

Partial Creating a unified router proxy interface over standard agent harnesses is straightforward, but running managed agent harnesses (sandboxed code execution, bidirectional streaming, process isolation) requires non-trivial infrastructure.

What it would actually take: A production version requires a fast API gateway (FastAPI/Go) orchestrating Docker/Firecracker microVM containers to execute agent environments safely. It needs persistent state management, token tracking, and protocol translation across fragmented proprietary agent interfaces. The hard part is secure, multi-tenant isolated execution environments with sub-second spin-up times.

Discussion

14 comments analyzed.

Competitors mentioned: OpenRouter (model routing equivalent), Codex (agent harness), Claude Code (agent harness), Local Claude implementations

Concerns raised: Unclear utility of routing across multiple harnesses vs. sticking with one, Harness lock-in and vendor service unreliability, Risk of becoming lowest-common-denominator API, Harness-specific features getting lost in abstraction, Coding scenarios may not benefit as much as white-collar use cases

Feature requests: Agent handoff protocol for continuing workflows across token limits, Smart routing for harness fallback and cost optimization, Harness-specific feature preservation without LCD API, Production performance tracing insights for combination selection

Competitors

Other products that read as similar to this one — 364 launches clear the similarity bar, closest 8 shown.

Attention rank: #180 of 365 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 286 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a agent / copilot tool for Agriculture yet.