harnessrouter

Source#

• Repository: HarnessRouter/harnessrouter
• Last source update: 2026-09-06
• Last verified: 2026-09-06

Tags#

Integration notes#

Framework-level abstraction; derive bounded worker contracts from concrete tasks and APIs in docs/examples.

worker.md example#

Starter worker.md contract mapped from this registry entry. Copy this file and adapt schemas, constraints, and statuses for your task.

---
id: harnessrouter-repo-derived-worker
name: harnessrouter Repo-Derived Worker
version: 1.0.0
source_registry_url: https://worker.md/registry/harnessrouter/
source_repository: https://github.com/HarnessRouter/harnessrouter
repository_default_branch: main
repository_language: Python
repository_license: Apache-2.0
repository_updated_at: 2026-09-06
worker_mode: agent-orchestration-worker
derivation_method: github_repository_metadata_plus_raw_readme
derivation_confidence: 0.95
derived_on: 2026-09-06
tags:
  - agent-api
  - agent-framework
  - agent-harness
  - ai-agents
  - ai-infrastructure
  - coding-agent
---

# harnessrouter Repo-Derived Worker

## Repo-derived summary
- Registry summary: 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, ...
- Repository description: 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.
- Stars (snapshot): 664
- Primary language: Python
- Worker mode classification: agent-orchestration-worker

## Extracted from
- https://github.com/HarnessRouter/harnessrouter
- https://github.com/HarnessRouter/harnessrouter/blob/main/README.md
- https://img.shields.io/docker/pulls/harnessrouter/harnessrouter?logo=docker&logoColor=white
- https://img.shields.io/badge/Follow-%40HARNESSROUTER-000000?logo=x&logoColor=white
- https://hub.docker.com/r/harnessrouter/harnessrouter/tags

## Evidence notes (from repository text)
- README summary paragraph: **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 https://unifiedharnessprotocol.org, the open standard the hosted service implements too.
- Run agent harnesses on your own machine.
- **Run agent harnesses on your own machine.** One container, your own API keys, your
- Six steps, and at the end of them you have a running instance, a signed-in console, and an agent
- `-v harnessrouter:/data` is where everything durable lives: the database, your files, and the agent
- exactly one thing: every agent CLI runs as its own per-session user, which owns that session's

## Installation hints found in README
- `pip install -e protocol/conformance`

## worker.md contract (derived starter)
Purpose: Execute one orchestrated agent task as a bounded worker step.

### Input schema
```json
{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "run_id",
    "task",
    "context"
  ],
  "properties": {
    "run_id": {
      "type": "string"
    },
    "task": {
      "type": "string"
    },
    "context": {
      "type": "object"
    }
  }
}
```

### Output schema
```json
{
  "type": "object",
  "additionalProperties": false,
  "required": [
    "run_id",
    "status",
    "result"
  ],
  "properties": {
    "run_id": {
      "type": "string"
    },
    "status": {
      "type": "string",
      "enum": [
        "ok",
        "retryable_error",
        "invalid_request",
        "invalid_output"
      ]
    },
    "result": {
      "type": "object"
    }
  }
}
```

### Constraints
- timeout_seconds: 30
- max_attempts: 2
- idempotency_key: run_id
- status_enum: [ok, retryable_error, invalid_request, invalid_output]
- notes: adapt to concrete APIs/classes documented in this repository before production use

## How this should be used
1. Treat this file as a repo-derived starter profile, not a claim of an official repository API contract.
2. Replace schemas with exact interfaces from code/docs you adopt.
3. Keep execution bounded and auditable using worker protocol constraints.

How to use#

• Save this as a worker spec file (for example: harnessrouter-my-task.worker.md).
• Replace the input/output schemas and purpose with your real bounded task.
• Enforce schema validation + timeout + retry policy in your runtime before production use.

Citation#

Reference URL: https://worker.md/registry/harnessrouter/

Source URL: https://github.com/HarnessRouter/harnessrouter