HarnessRouter: The OpenRouter for Agent Harnesses, Not Just Models
(including System One by Jev)
Devs just open-sourced a plug-and-play infrastructure layer that lets you run any harness under a single interface, like:
- Codex
- Hermes
- Claude code
- DeepSeek Harness
- System One, powered by Jev
- And 9 more agent harnesses
This means you can bring Jev into the same product that already uses Codex, Claude Code, or another supported harness, without writing another implementation for sessions, streaming, files, cancellation, and failure handling.
You can find link to the repo in the first comment.
The harnesses run locally, and the Unified Harness Protocol (UHP) defines the common task interface with an OpenAI Responses-compatible API.
The core project is real and accurately described — but one specific claim (Jev/System One being one of its supported harnesses) doesn't match what I could find documented anywhere, and is arguably inconsistent with how Jev has been described elsewhere.
HarnessRouter and UHP are real. Launched via Y Combinator on August 17, 2026, with a Community Edition and the Unified Harness Protocol (UHP) as an open standard, positioned explicitly as bringing the world's best AI agents into your app, with one API.
"OpenRouter for agent harnesses" is a fair analogy, not an exaggeration. HarnessRouter's own materials describe it as the world's first unified interface for agent harnesses, where your product sends a task through one agent API and HarnessRouter runs the harness you choose and returns completed work.
"Sessions, streaming, files, cancellation, and failure handling" — confirmed nearly verbatim. The project's own README states it: run Codex, Claude Code, Hermes, PI, DSH, and more through one API, with sessions, streaming, files, cancellation, and failure handling.
"Runs locally... Unified Harness Protocol with an OpenAI Responses-compatible API" — confirmed exactly. HarnessRouter implements UHP and provides an OpenAI Responses-compatible API, and is explicitly self-hosted, on your own infrastructure with your own provider keys.
The specific harness list: mostly confirmed, but "System One by Jev" is the outlier. The self-hosting guide lists Codex, Claude Code, Hermes, DeepSeek Harness, Gemini CLI, OpenCode, Qwen Code, Cline, and Goose as supported backends — that's the "5 named + 9 more" shape your post describes. But I found no source listing "System One" or Jev as one of HarnessRouter's supported harnesses. This also seems conceptually off: everywhere else Jev has been described in this thread, it's framed as a lightweight decision model that other applications (jev-ultrafast, jev-desktop) embed inside their own tool-execution loop — not as a standalone "harness" with its own session, file editing, and planning loop the way Codex or Claude Code are. Calling "System One, powered by Jev" one of the interchangeable harnesses alongside Codex and Claude Code may be a mismatch between two separate, real projects rather than an accurate feature of HarnessRouter itself. Worth double-checking directly against the current repo before repeating this claim.