Comparison
AgentGuard vs claude-mem
Verdict
Pick AgentGuard when license: AgentGuard is MIT, claude-mem is Apache-2.0; pick claude-mem when license: claude-mem is Apache-2.0, AgentGuard is MIT.
Markdown twin · AgentGuard alternatives · claude-mem alternatives
GraphCanon updated today
vs
Trust & integrity
| Signal | AgentGuard | claude-mem |
|---|---|---|
| Maintenance | Slowing (348d since push) As of today · github_public_v1 | Very active (1d since push) As of 4d · github_public_v1 |
| Provenance | Not a fork · Personal account As of today · github_public_v1 | Not a fork · Personal account As of 4d · github_public_v1 |
| OSV dependency advisories | Published findings As of today · osv@v1 | No lockfile (source not queried) As of 4d · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- AgentGuard
- Real-time guardrail that shows token spend & kills runaway LLM/agent loops.
- claude-mem
- Persistent Context Across Sessions for Every Agent
Stars
- AgentGuard
- 160
- claude-mem
- 87k
Forks
- AgentGuard
- 9
- claude-mem
- 7.5k
Open issues
- AgentGuard
- 1
- claude-mem
- 252
Language
- AgentGuard
- JavaScript
- claude-mem
- JavaScript
Adopt for
- AgentGuard
- -
- claude-mem
- claude-mem provides persistent context across sessions, leveraging AI to capture and compress agent activity.
Persona
- AgentGuard
- -
- claude-mem
- -
Runtime
- AgentGuard
- -
- claude-mem
- -
License
- AgentGuard
- MIT
- claude-mem
- Claude-Mem is distributed under the Apache License 2.0, allowing it to be freely used in a variety of development and production environments while maintaining clear licensing terms.
Last pushed
- AgentGuard
- Jul 31, 2025
- claude-mem
- Jul 9, 2026
Categories
- AgentGuard
- AI Agents, Inference & Serving, LLM Frameworks
- claude-mem
- AI Agents, Inference & Serving
Trust and health
Maintenance
- AgentGuard
- Slowing (36%)
- claude-mem
- Very active (96%)
Days since push
- AgentGuard
- 348d
- claude-mem
- 1d
Open issues (now)
- AgentGuard
- 1
- claude-mem
- 252
OSV dependency advisories
- AgentGuard
- Published findings
- claude-mem
- No lockfile (source not queried)
Full report
- AgentGuard
- Trust report
- claude-mem
- Trust report
Shared compatibility
- Node.js · AgentGuard: Node.js runtime · claude-mem: Node.js runtime
Choose AgentGuard if…
- License: AgentGuard is MIT, claude-mem is Apache-2.0.
- Tags unique to AgentGuard: anthropic, anthropic-claude, cost-monitoring, debugging.
- Also covers LLM Frameworks.
When NOT to use AgentGuard
- Last GitHub push was 349 days ago (slowing maintenance, Jul 31, 2025). Validate activity before betting a new project on AgentGuard.
- AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
- Inference & Serving: Self-hosting rarely beats a hosted API on cost until you have steady, high-volume traffic.
- LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.
Choose claude-mem if…
- License: claude-mem is Apache-2.0, AgentGuard is MIT.
- Requirements: Requires Node.js v20.0.0 or higher.; Must have the latest version of Claude Code with plugin support.; Auto-installs Bun (JavaScript runtime and process manager) if not already present.; Requires uv (Python package for vector search), auto-installation supported..
- Tags unique to claude-mem: ai-memory, chromadb, claude, long-term-memory.
- When you require seamless and persistent context continuity between different session interactions with Claude Code or other supported agents.
When NOT to use claude-mem
- When working in environments where Node.js v20.0.0 or higher cannot be installed, as claude-mem requires this version to operate.
- If your specific AI agent or tool does not integrate with the supported frameworks listed (e.g., Claude Code, OpenClaw), making context persistence ineffective for your workflow.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (dipampaul17/AgentGuard) · observed Jul 15, 2026
- GitHub forks (dipampaul17/AgentGuard) · observed Jul 15, 2026
- Last push (dipampaul17/AgentGuard) · observed Jul 31, 2025
- License file (MIT) · observed Jul 15, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
- GitHub stars (thedotmack/claude-mem) · observed Jul 11, 2026
- GitHub forks (thedotmack/claude-mem) · observed Jul 11, 2026
- Last push (thedotmack/claude-mem) · observed Jul 9, 2026
- License file (Apache-2.0) · observed Jul 11, 2026
- Decision facts (enrichment) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: AgentGuard 160 · claude-mem 87k (synced Jul 15, 2026).
Common questions
- What is the difference between AgentGuard and claude-mem?
- AgentGuard: Real-time guardrail that shows token spend & kills runaway LLM/agent loops.. claude-mem: Persistent Context Across Sessions for Every Agent. See the comparison table for live GitHub stats and shared categories.
- When should I choose AgentGuard over claude-mem?
- Choose AgentGuard over claude-mem when License: AgentGuard is MIT, claude-mem is Apache-2.0; Tags unique to AgentGuard: anthropic, anthropic-claude, cost-monitoring, debugging; Also covers LLM Frameworks.
- When should I choose claude-mem over AgentGuard?
- Choose claude-mem over AgentGuard when License: claude-mem is Apache-2.0, AgentGuard is MIT; Requirements: Requires Node.js v20.0.0 or higher.; Must have the latest version of Claude Code with plugin support.; Auto-installs Bun (JavaScript runtime and process manager) if not already present.; Requires uv (Python package for vector search), auto-installation supported.; Tags unique to claude-mem: ai-memory, chromadb, claude, long-term-memory; When you require seamless and persistent context continuity between different session interactions with Claude Code or other supported agents.
- When should I avoid AgentGuard?
- Last GitHub push was 349 days ago (slowing maintenance, Jul 31, 2025). Validate activity before betting a new project on AgentGuard. AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. Inference & Serving: Self-hosting rarely beats a hosted API on cost until you have steady, high-volume traffic. LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.
- When should I avoid claude-mem?
- When working in environments where Node.js v20.0.0 or higher cannot be installed, as claude-mem requires this version to operate. If your specific AI agent or tool does not integrate with the supported frameworks listed (e.g., Claude Code, OpenClaw), making context persistence ineffective for your workflow.
- Is AgentGuard or claude-mem more popular on GitHub?
- claude-mem has more GitHub stars (86,816 vs 160). Stars measure visibility, not whether either tool fits your constraints.
- Are AgentGuard and claude-mem open source?
- Yes - both are open-source projects on GitHub (AgentGuard: MIT, claude-mem: Apache-2.0).
- Where can I find alternatives to AgentGuard or claude-mem?
- GraphCanon lists graph-backed alternatives at AgentGuard alternatives and claude-mem alternatives (AgentGuard markdown twin, claude-mem markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, AgentGuard or claude-mem?
- AgentGuard: Slowing. claude-mem: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for AgentGuard and claude-mem?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: AgentGuard trust report; claude-mem trust report.