Skip to content

HarnessRouter Community Edition: the self-hosted, Apache-2.0 edition of the unified interface for agent harnesses. Run Codex, Claude Code, Hermes, PI, DSH, and more through one API, with sessions, streaming, files, cancellation, and failure handling. Implements the Unified Harness Protocol (UHP), an open standard. Your keys, your infrastructure.

docs: add community health files, naming policy, README launch-alignment

kuanzema4ddce207ae5f
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000..b8275d7b
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,43 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [email protected]. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 00000000..33751151
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,23 @@
+# Contributing
+
+Contributions are welcome, and so are questions.
+
+## Where things go
+
+- Proposals and bug reports: GitHub Issues.
+- Discussion: the HarnessRouter Discord community, https://discord.gg/nPcbwqVPb2
+- Security vulnerabilities: privately, per [SECURITY.md](SECURITY.md). Not in a public issue.
+
+## Substantial changes: describe before you build
+
+For anything beyond a small fix, open an issue first. Describe the problem you are solving, the change you propose, and its expected impact, before writing the implementation. Once a maintainer agrees on the direction, either you or a maintainer implements it.
+
+Small, obvious fixes such as typos or a clear bug with an equally clear fix can go straight to a pull request.
+
+## Changes to the protocol
+
+The Unified Harness Protocol has a stricter process, because a specification, a reference implementation, and a conformance suite have to stay in step. If your change touches the protocol, follow [protocol/GOVERNANCE.md](protocol/GOVERNANCE.md): open a UHP Enhancement Proposal (UEP) as an issue labelled `uep` with Problem, Proposal, Compatibility, and Alternatives. Maintainers respond within 10 working days. An accepted UEP ships as one pull request that updates the specification, the schema, the reference implementation, a conformance test, and the changelog together.
+
+## License
+
+By contributing, you agree that your contribution is licensed under the Apache License 2.0, the same license as this repository.
diff --git a/README.md b/README.md
index 8d9b0493..ceae2e9a 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,7 @@
# HarnessRouter
-**Run agentic coding harnesses on your own machine.** One container, your own API keys, your
-own data. Configure a harness, give it work, watch it run — no account, no cloud, no telemetry.
+**Run agent harnesses on your own machine.** One container, your own API keys, your
+own data. Configure a harness, give it work, watch it run, with no account, no cloud, and no telemetry. Community Edition implements the [Unified Harness Protocol (UHP)](https://unifiedharnessprotocol.org), the open standard the hosted service implements too.
```bash
docker run -d -p 3000:3000 -v harnessrouter:/data \
@@ -19,20 +19,18 @@ That's the whole install. State is SQLite and files on one Docker volume.
## What it is
-A *harness* is a configured agent: a backend runtime, a model, instructions, and limits. A
-*task* is one run of that harness — a real conversation against a real POSIX workspace with
-bash and git, streamed back as it happens.
+An *agent harness* is the runtime layer around a model; Codex, Claude Code, and Hermes are harnesses. In this repo's API you also create *harness* objects: a saved configuration whose `base` is one of those runtimes, plus a model, instructions, and limits. A *task* is one run of that configuration, a real conversation against a real POSIX workspace with bash and git, streamed back as it happens.
-HarnessRouter gives you the full protocol for both: an OpenAI **Responses-compatible** API for
+HarnessRouter Community Edition implements UHP for both: an OpenAI **Responses-compatible** API for
running turns, harness CRUD, sessions, streaming, cancellation, and idempotency. The console is
-a thin client over that API — anything the UI does, you can do from `curl`.
+a thin client over that API; anything the UI does, you can do from `curl`.
**The console is the hosted product's console.** Not a cut-down rebuild: the same pages, the
-same components, the same API client. Surfaces that need a service a single box doesn't have —
-accounts, billing, marketplace — are simply not shown.
+same components, the same API client. Surfaces that need a service a single box doesn't have,
+such as accounts, billing, and marketplace, are simply not shown.
-**Backends:** Claude Code, OpenAI Codex, and Hermes. They are installed on first run rather than
-shipped in the image — Claude Code is distributed under Anthropic's own terms and hermes-agent
+**Supported harnesses:** Codex, Claude Code, and Hermes. They are installed on first run rather than
+shipped in the image. Claude Code is distributed under Anthropic's own terms and hermes-agent
declares no license, so neither can be redistributed. Set `HR_BACKENDS` to choose which you want,
and review each tool's license before enabling it.
@@ -241,14 +239,15 @@ why this is genuinely the same codebase rather than a fork that drifts.
## The Unified Harness Protocol
This repository is both an implementation and a standard. The protocol the gateway speaks is
-specified, versioned and testable in [`protocol/`](protocol/):
+specified, versioned and testable in [`protocol/`](protocol/), and documented at
+[unifiedharnessprotocol.org](https://unifiedharnessprotocol.org):
| | |
|---|---|
| [Specification](protocol/versions/2026-08-11/) | Ten normative chapters, version `2026-08-11` |
| [Machine-readable](protocol/schema/) | OpenAPI 3.1 + JSON Schema 2020-12, generated from one source |
-| [Conformance suite](protocol/conformance/) | 47 runnable checks — passing it is what "conformant" means |
-| [Governance](protocol/GOVERNANCE.md) | How the standard changes: prose first, three artifacts together |
+| [Conformance suite](protocol/conformance/) | 47 runnable checks; passing it is what "conformant" means, and what earns the right to the UHP name |
+| [Governance](protocol/GOVERNANCE.md) | How the standard changes, and the naming and conformance policy |
This edition is the reference implementation and
[passes at class Full](protocol/conformance/reports/harnessrouter-ce-0.3.0.json). **The standard can
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 00000000..41ae9722
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,22 @@
+# Security Policy
+
+HarnessRouter Community Edition runs agent CLIs with your own provider keys and executes their work in local workspaces with bash, git, and a filesystem. Treat any instance as capable of running code with the credentials you give it, and keep it off public networks unless you have set a password and put TLS in front of it.
+
+## Reporting a vulnerability
+
+Please report security issues privately. Do not open a public GitHub issue for a vulnerability.
+
+Two private channels:
+
+- GitHub private vulnerability reporting: use the "Report a vulnerability" button under this repository's Security tab.
+
+Include what is needed to reproduce it: affected version or commit, environment, steps, expected impact, and a proof of concept if you have one.
+
+We aim to acknowledge a report within 10 working days, agree on a fix and a disclosure timeline with you, and credit you when the fix ships if you want the credit.
+
+## Scope
+
+In scope: the gateway, runner, console, adapters, and the protocol implementation in this repository.
+
+Out of scope: the agent CLIs themselves (Codex, Claude Code, Hermes), installed on first run under their own licenses and with their own security contacts; and issues that require an already-compromised host or a credential you supplied to the instance.
diff --git a/protocol/GOVERNANCE.md b/protocol/GOVERNANCE.md
index e9a2b5a6..ed102463 100644
--- a/protocol/GOVERNANCE.md
+++ b/protocol/GOVERNANCE.md
@@ -73,3 +73,13 @@ per [VERSIONING.md](VERSIONING.md), published with a migration note.
report alongside the claim is expected. There is no certification body, no fee, and no logo
programme — the suite is the authority, it is in this repository, and anyone can run it against
anyone's server.
+
+## Naming and conformance
+
+The canonical name of this standard is the Unified Harness Protocol (UHP). Its site is https://unifiedharnessprotocol.org.
+
+Apache-2.0 grants rights to the code and the specification under its terms. It does not grant rights to the protocol name. "Unified Harness Protocol" and "UHP" are marks of [LEGAL_ENTITY].
+
+An implementation may describe itself as "UHP-compatible" or say it "implements UHP" only if it passes the conformance suite in [`conformance/`](conformance/). Passing that suite is the definition of conformant for this project. Non-conformant implementations, partial implementations, and modified forks must not use the name in a way that implies compatibility. Stating factually that a product "works with" or "connects to" UHP is fine.
+
+Trademark and compatibility-claim questions can be sent to [email protected].