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

Integration pattern

Continue or revise the same product task.

Continue and revise should feel like one product task evolving, not a new unrelated run.

State to save

  • Product user or tenant ID.
  • Feature key and configured agent ID.
  • Session ID and last response ID.
  • Artifact records and preview state.
  • Terminal status and incomplete details when available.

Request

Send the follow-up text with previous_response_id and metadata.session_id. Use a new Idempotency-Key for the new follow-up request.

Open standard

Because a UHP session is a chain of responses, the revise flow only needs the last response id and session id you stored — the earlier turns' context comes back with the continuation. See the Sessions chapter in the UHP spec.

Create API Key

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