Comparison
awesome-argo vs claude-mem
Verdict
Pick awesome-argo when tags unique to awesome-argo: awesome-lists, awesome, argo-workflows, argo-rollouts; pick claude-mem when 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..
Markdown twin · awesome-argo alternatives · claude-mem alternatives
GraphCanon updated today
vs
Trust & integrity
| Signal | awesome-argo | claude-mem |
|---|---|---|
| Maintenance | Active (23d since push) As of today · github_public_v1 | Very active (1d since push) As of today · github_public_v1 |
| Provenance | Not a fork · Organization account As of today · github_public_v1 | Not a fork · Personal account As of today · github_public_v1 |
| Security (OSV) | No lockfile As of today · none | No lockfile As of today · none |
Tagline
- awesome-argo
- A curated list of awesome projects and resources related to Argo (a CNCF graduated project)
- claude-mem
- Persistent Context Across Sessions for Every Agent
Stars
- awesome-argo
- 2.5k
- claude-mem
- 87k
Forks
- awesome-argo
- 196
- claude-mem
- 7.5k
Open issues
- awesome-argo
- 2
- claude-mem
- 252
Language
- awesome-argo
- -
- claude-mem
- JavaScript
Adopt for
- awesome-argo
- -
- claude-mem
- claude-mem provides persistent context across sessions, leveraging AI to capture and compress agent activity.
Persona
- awesome-argo
- -
- claude-mem
- -
Runtime
- awesome-argo
- -
- claude-mem
- -
License
- awesome-argo
- Apache-2.0
- 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
- awesome-argo
- Jun 18, 2026
- claude-mem
- Jul 9, 2026
Categories
- awesome-argo
- AI Agents, Vector Databases, Inference & Serving
- claude-mem
- AI Agents, Inference & Serving
Trust and health
Maintenance
- awesome-argo
- Active (82%)
- claude-mem
- Very active (96%)
Days since push
- awesome-argo
- 23d
- claude-mem
- 1d
Open issues (now)
- awesome-argo
- 2
- claude-mem
- 252
Owner type
- awesome-argo
- Organization
- claude-mem
- User
Full report
- awesome-argo
- Trust report
- claude-mem
- Trust report
Choose awesome-argo if…
- Tags unique to awesome-argo: awesome-lists, awesome, argo-workflows, argo-rollouts.
- Also covers Vector Databases.
- Leaner open-issue backlog (2).
When NOT to use awesome-argo
- AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
- Vector Databases: Don't reach for a dedicated vector DB under ~100k vectors; pgvector on your existing Postgres is simpler to operate.
- Inference & Serving: Self-hosting rarely beats a hosted API on cost until you have steady, high-volume traffic.
Choose claude-mem if…
- 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: chromadb, ai-memory, 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 (akuity/awesome-argo) · observed Jul 11, 2026
- GitHub forks (akuity/awesome-argo) · observed Jul 11, 2026
- Last push (akuity/awesome-argo) · observed Jun 18, 2026
- License file (Apache-2.0) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 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: awesome-argo 2.5k · claude-mem 87k (synced Jul 11, 2026).
Common questions
- What is the difference between awesome-argo and claude-mem?
- awesome-argo: A curated list of awesome projects and resources related to Argo (a CNCF graduated project). claude-mem: Persistent Context Across Sessions for Every Agent. See the comparison table for live GitHub stats and shared categories.
- When should I choose awesome-argo over claude-mem?
- Choose awesome-argo over claude-mem when Tags unique to awesome-argo: awesome-lists, awesome, argo-workflows, argo-rollouts; Also covers Vector Databases; Leaner open-issue backlog (2).
- When should I choose claude-mem over awesome-argo?
- Choose claude-mem over awesome-argo when 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: chromadb, ai-memory, 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 awesome-argo?
- AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. Vector Databases: Don't reach for a dedicated vector DB under ~100k vectors; pgvector on your existing Postgres is simpler to operate. Inference & Serving: Self-hosting rarely beats a hosted API on cost until you have steady, high-volume traffic.
- 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 awesome-argo or claude-mem more popular on GitHub?
- claude-mem has more GitHub stars (86,816 vs 2,457). Stars measure visibility, not whether either tool fits your constraints.
- Are awesome-argo and claude-mem open source?
- Yes - both are open-source projects on GitHub (awesome-argo: Apache-2.0, claude-mem: Apache-2.0).
- Where can I find alternatives to awesome-argo or claude-mem?
- GraphCanon lists graph-backed alternatives at awesome-argo alternatives and claude-mem alternatives (awesome-argo 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, awesome-argo or claude-mem?
- awesome-argo: Active. 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 awesome-argo and claude-mem?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: awesome-argo trust report; claude-mem trust report.