Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • What’s the pitch for a harness router?iirc codex has codex app server, pi also has a reusable core.
  • Think of it as OpenRouter, but for different agent harnesses, not models. Instead of sticking to any one harness, you can route to and use any of them through a unified API
  • How does this handle harness-specific features without becoming a lowest-common-denominator API?
  • Here's Kuanze, co-founder of HarnessRouter. Before building HarnessRouter, I was building an entire harness to power other products. Building a harness was pretty fun for me. I enjoyed and learned quite a lot through building it.

    However, Richard asked me a question: how do you plan to keep up with the iteration speed of harnesses like Codex and Claude code. That question leads to the solution that we are delivering to the community today.

    From our perspective, the agent harness is becoming an independent infra layer, and it should become a dev tool. Our goal is to make agent harnesses plug-and-play solution for all developers, so they can skip rebuilding the infra layer and focus on shipping product features.

    We welcome all comments, feedbacks, protocol contributions, and feature suggestions.

  • This could benefit from a agent handoff protocol where it can communicate and continue different workflows once your tokens are done or a model couldnt achieve what you expect.