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.
OpenRath earned a place on the map:
How we mapped it:
- alternative to
deepagents — Both are composable Python agent libraries with sub-agents and durable state. DeepAgents rides LangGraph and its ecosystem; OpenRath rebuilds the primitives around Session and ships its own durable runtime, which is more to learn but fewer layers to fight.
- pairs well with
shepherd — OpenRath already records Runs, Events and Checkpoints. Shepherd's reversible Git-like execution traces are the layer above that — fork, replay and revert a run before its outputs are released.
If you want it visible in your README, every mapped repo has a badge:
[](https://stackmap.shipwithai.xyz/repos/Rath-Team/openrath?utm_source=badge)
It renders as StackMap | ↔ 7 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.
OpenRath earned a place on the map:
How we mapped it:
deepagents— Both are composable Python agent libraries with sub-agents and durable state. DeepAgents rides LangGraph and its ecosystem; OpenRath rebuilds the primitives around Session and ships its own durable runtime, which is more to learn but fewer layers to fight.shepherd— OpenRath already records Runs, Events and Checkpoints. Shepherd's reversible Git-like execution traces are the layer above that — fork, replay and revert a run before its outputs are released.If you want it visible in your README, every mapped repo has a badge:
It renders as
StackMap | ↔ 7 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.