HarnessRouter

Navigate HarnessRouter

Search the site

  • HarnessRouter Community EditionOpen-source agent harness infrastructure and the Unified Harness Protocol.Product
  • Harness catalogSupported harness IDs and source-backed integration references.Harnesses
  • Care Prep BenchmarkThe same task compared across Codex, Claude Code, and Hermes configurations.Benchmarks
  • Harness rankingsPublic attributed usage across reviewed agent harnesses.Product
  • ExamplesSee how agent-backed features return finished work inside a product.Product
  • PricingPlans and usage pricing for HarnessRouter.Product
  • Hermes AgentAn open-source, persistent AI agent with memory, reusable skills, built-in tools, browser automation, scheduled tasks, and subagents.Harnesses
↑↓ Navigate↵ OpenEsc Close
Sign up

Core concept

A response is one turn inside a session.

Save the response ID and session ID from the stream. Your product needs both to recover, continue, cancel, and fetch artifacts.

Identifiers

response.id
The runtime response identifier. Use it for continuation as previous_response_id.
response.metadata.session_id
The persistent session identifier. Use it for polling, turns, files, cancel, and archive.

Terminal states

Streaming uses events such as response.completed, response.incomplete, and response.failed. Session polling reports a successful turn as status: "done", not completed.

Open standard

Saving response.id for continuation and response.metadata.session_id for recovery follows the UHP session model, which chains follow-up turns on the previous response id rather than on the session itself. See Sessions in the UHP specification.

Create API Key

Ready to run this against a live workspace? Keys take under a minute.