HarnessRouter
A self-hosted routing infrastructure layer for agent harnesses that wraps multiple agent harnesses as pluggable backends, implements the Unified Harness Protocol, and exposes an OpenAI Responses-compatible interface.
Timeline (last 90 days)
HarnessRouter is an infrastructure layer that uniformly wraps existing Agent harnesses (such as Codex, Claude Code, Hermes, PI, DSH, etc.) as pluggable backends, providing services externally through a single API.
HarnessRouter implements the open standard Unified Harness Protocol (UHP) and exposes an interface compatible with OpenAI Responses.
The HarnessRouter project uses the Apache-2.0 license, is a self-hosted solution, and does not bundle models or provide trial keys.
HarnessRouter supports persistent sessions, streaming progress, file and artifact management, task cancellation, and structured failure reporting.
The Docker command to launch HarnessRouter is `docker run -d --name harnessrouter -p 127.0.0.1:3000:3000 -v harnessrouter:/data harnessrouter/harnessrouter`.
HarnessRouter needs to be run with Docker, requires about 4GB of disk space, and provides default login credentials (username harnessrouter, password harnessrouter).
HarnessRouter adopts a per-session user isolation strategy; the Runner dynamically allocates a separate Linux user for each Agent session, so the entry script and the Runner require root privileges, and passing the --user parameter is officially prohibited.
HarnessRouter explicitly chooses the Bring Your Own Key (BYOK) deployment model; users must configure provider API keys themselves, and when no integration is configured the console can be logged into but no models are available.
The Chinese quick start document reminds users to change the default password, and to bind the instance to localhost before changing it; saving changes briefly restarts the console and logs out other browser sessions.
All Facts (9)
HarnessRouter is an infrastructure layer that uniformly wraps existing Agent harnesses (such as Codex, Claude Code, Hermes, PI, DSH, etc.) as pluggable backends, providing services externally through a single API.
50%UnverifiedHarnessRouter implements the open standard Unified Harness Protocol (UHP) and exposes an interface compatible with OpenAI Responses.
50%UnverifiedThe HarnessRouter project uses the Apache-2.0 license, is a self-hosted solution, and does not bundle models or provide trial keys.
50%UnverifiedHarnessRouter supports persistent sessions, streaming progress, file and artifact management, task cancellation, and structured failure reporting.
50%UnverifiedThe Docker command to launch HarnessRouter is `docker run -d --name harnessrouter -p 127.0.0.1:3000:3000 -v harnessrouter:/data harnessrouter/harnessrouter`.
50%UnverifiedHarnessRouter needs to be run with Docker, requires about 4GB of disk space, and provides default login credentials (username harnessrouter, password harnessrouter).
50%UnverifiedHarnessRouter adopts a per-session user isolation strategy; the Runner dynamically allocates a separate Linux user for each Agent session, so the entry script and the Runner require root privileges, and passing the --user parameter is officially prohibited.
50%UnverifiedHarnessRouter explicitly chooses the Bring Your Own Key (BYOK) deployment model; users must configure provider API keys themselves, and when no integration is configured the console can be logged into but no models are available.
50%UnverifiedThe Chinese quick start document reminds users to change the default password, and to bind the instance to localhost before changing it; saving changes briefly restarts the console and logs out other browser sessions.
50%