Not a task — informational heads-up for the maintainers, nothing to implement. Close it freely.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
harnessrouter earned a place on the map:
How we mapped it:
- alternative to
omnigent — Both are meta-layers over Claude Code, Codex, Hermes, Pi and DSH that let you swap the harness; omnigent is a developer-facing meta-harness, harnessrouter is a self-hosted API service with sessions, files and a protocol spec.
- alternative to
agentdock — Same job — give a backend one runtime API with session-scoped runs, streaming, approvals and cancellation — but agentdock is a TypeScript library you embed, harnessrouter wraps existing third-party harness CLIs behind a service.
If you want it visible in your README, every mapped repo has a badge:
[](https://stackmap.shipwithai.xyz/repos/HarnessRouter/harnessrouter?utm_source=badge)
It renders as StackMap | ↔ 5 typed links and links to the page above. Static JSON — the count updates itself as the map changes, nothing for you to maintain.
If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.
Hi — I curate StackMap, a hand-curated knowledge graph of open-source AI/agent tools. Every entry is human-reviewed: a summary, an opinionated note on when to use it (and when not), and typed edges to what it pairs with or competes against — with the why written down.
harnessrouter earned a place on the map:
How we mapped it:
omnigent— Both are meta-layers over Claude Code, Codex, Hermes, Pi and DSH that let you swap the harness; omnigent is a developer-facing meta-harness, harnessrouter is a self-hosted API service with sessions, files and a protocol spec.agentdock— Same job — give a backend one runtime API with session-scoped runs, streaming, approvals and cancellation — but agentdock is a TypeScript library you embed, harnessrouter wraps existing third-party harness CLIs behind a service.If you want it visible in your README, every mapped repo has a badge:
It renders as
StackMap | ↔ 5 typed linksand links to the page above. Static JSON — the count updates itself as the map changes, nothing for you to maintain.If any of this misrepresents the project — an edge you'd dispute, a sharper "when NOT to use" — reply here and a human fixes it. And feel free to just close this issue; it's only a heads-up.