Genesys vs Shepherd

Genesys and Shepherd are both agent frameworks tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Genesys

Genesys stores what you share in a causal graph you own, then surfaces that context to any app that speaks MCP — so Claude already knows what you told ChatGPT, without you repeating yourself. The graph explains its own reasoning: ask why it remembers something and you get the actual chain of connections, not a confidence score with nothing behind it. Memories fade by a scoring formula tied to relevance and reactivation, so stale data drops out without silently deleting things that still matter. The free tier caps writes at 300 stores per month — heavy users or teams running MCP agents hit that ceiling, then face a choice.

Shepherd

SHEPHERD is a Python substrate from Stanford and Northeastern that turns an agent's execution into a Git-like, reversible trace — so a supervising meta-agent can observe, intercept, fork, and revert any step without rebuilding that capability from scratch each time. The vendor-published benchmark numbers are specific: a supervisor meta-agent lifted pair-coding pass rate from 28.8% to 54.7% on CooperBench; a counterfactual repair meta-agent beat MetaHarness on Terminal-Bench 2.0 by 12.8% while cutting wall-clock time by 58%. The framework is research-grade and open-source, installed via pip. Teams outside the specific use cases the paper targets — runtime intervention, counterfactual optimization, and agentic RL training — will find precious little guidance on how far the substrate stretches.

Attribute	Genesys	Shepherd
Pricing	Paid	Free
Price	$0-$8/mo	—
Free trial	No	No
Open source	Yes	Yes
Has API	Yes	No
Self-hosted option	Yes	Yes
Platforms	Web, Python (pip)	Python
Released	—	2026
Pros	Cross-app memory over MCP, which means context you shared in ChatGPT appears in Claude without any manual sync — eliminating the re-introduction loop that breaks multi-tool workflows. Causal graph with inspect-and-correct capability, so when the memory layer gets something wrong you can trace why and fix it at the source rather than working around a black box. Evidence-based memory decay via a published scoring formula, which means stale context fades out without silently deleting nodes that are still connected and active — a common failure mode in simpler vector-store approaches. Open-source AGPL-3.0 engine with pip install and self-host support, so teams with data residency requirements or high write volumes can run their own backend instead of depending on the hosted service. Permanent, on-demand deletion with no retention games — the vendor states reading is never gated, so your memory graph does not go dark if you stop paying.	Git-like reversible execution traces built into the substrate, so a meta-agent can revert a worker to any prior state without custom snapshot logic that teams would otherwise rebuild from scratch on every project. Fork-and-replay from any past checkpoint, which means a counterfactual optimizer can test a corrected decision path without re-running the entire prior sequence — the vendor reports 58% lower wall-clock versus MetaGarness on Terminal-Bench 2.0. Meta-agents and worker agents share the same @task code interface, so the control layer does not require a separate DSL or framework to learn — it is plain Python decorated functions. Open-source with pip install and self-hosting support, so teams running sensitive codebases can keep execution fully on-premise with no data leaving their environment. Intercept hooks let a meta-agent catch a destructive action before it lands, rather than reading about it in a post-mortem transcript — the supervisor use case lifted CooperBench pass rate from 28.8% to 54.7%.
Cons	The free tier caps memory writes at 300 stores per month. An MCP agent that logs context on every turn hits this ceiling within a single moderately active project, forcing a choice between the paid hosted tier or standing up the self-hosted engine — which adds infrastructure overhead before you've validated anything. The graph is architected around a single personal memory, not a shared team workspace. Developers building multi-user products where agents need to carry context per-user at scale have no documented path to multi-tenant graph management — teams with that requirement will look at purpose-built agent memory backends like Mem0 or a custom vector store instead. MCP is the only integration protocol documented. Applications that do not speak MCP and cannot add a custom connector get no benefit from the graph — teams whose stack is locked to a non-MCP LLM API get nothing without building their own bridge.	The framework's documented capabilities cover exactly three use cases from the paper; teams that need meta-agent patterns outside runtime intervention, counterfactual optimization, or agentic RL training will find no templates, examples, or community patterns to lean on — they are extending a research prototype. There is no API, which means SHEPHERD cannot be called from a non-Python orchestration layer or integrated into an existing service mesh without a custom wrapper — teams with polyglot architectures hit this wall immediately and typically reach for a framework with a REST interface instead. The Claude CLI dependency in the interactive demo signals the substrate's current depth of LLM provider integration; teams that cannot or will not use Anthropic models during onboarding face an underdocumented offline path before they have validated the tool for their use case. Research-grade codebase with no paid support tier means production incidents land entirely on the team's own debugging of the substrate — organizations that need an SLA or vendor escalation path will abandon SHEPHERD before the first outage.

Bottom line

Genesys is paid while Shepherd is free; only Genesys exposes a public API. Choose based on which difference matters most for your workflow.

Frequently asked questions

What is the difference between Genesys and Shepherd?

Genesys is Paid and open source, while Shepherd is Free and open source. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Genesys better than Shepherd?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.