HarnessRouter is an open-source unified interface that lets product teams plug Codex, Claude Code, Hermes, and other supported agent harnesses into their products through one Agent API. It enables them to build and scale agent-powered products quickly without managing separate agent backends.
This is the 5th launch from HarnessRouter. View more
HarnessRouter Community Edition
Launching today
Plug-and-play managed agent harnesses in your product: Codex, Claude Code and Hermes through one API on your infrastructure, now open sourced under Apache 2.0. Switch harnesses without rebuilding your backend. Sessions, streaming, files, artifacts, cancellation, failure recovery, all handled. Model provider keys, state, and deliveries under your control. Gateway, Runner, Console in one Docker container. Ready-to-use starter kit apps as inspiration of possibilities.
Free
Launch Team / Built With
HarnessRouter
Hey Product Hunt 👋
Today we're launching HarnessRouter Community Edition. Think of us as OpenRouter, but for agent harnesses instead of models.
We built HarnessRouter because we used to rebuild the same backend every time we need an agent runtime behind a product. We used to build our own harness with LangGraph, agent SDK, pydantic, etc, just to find out our self-built harness performance is hard to compete with Codex, Claude Code, Hermes, etc. Once we switched our infra to leverage off-the-shelf harnesses instead of rebuilding, our agent feature delivery time is shortened from weeks to hours, and the agent quality is dramatically better. We want to advocate the same mindset to the builder community.
HarnessRouter Community Edition puts Codex, Claude Code, and Hermes behind a single API: sessions, streaming, files, artifacts, cancellation, and all the failure handling nobody enjoys writing. Pull and start with one Docker container. Your credentials, state, and files never leave your infrastructure.
In addition to the product itself, we are also publishing Unified Harness Protocol. The Unified Harness Protocol standardizes how an application talks to an agent harness. The protocol covers harness selection and configuration, task execution, streaming events, sessions, file management, cancellation, error handling, and result delivery.
One more thing: harness agents are good at far more than coding. We're shipping open source starter kits across a bunch of agentic use cases (PPT building, Spreadsheet creating, BI/Dashboard creating, Video editing, etc). The use cases we're most curious about are the ones we haven't thought of.
We would love to learn two things from ProductHunt community:
Which harness should we support next?
Where does the abstraction leak for what you're building?
We're around all day.