AgentMemory vs Stele

AgentMemory

Agents

Stele

Agents

Tagline

AgentMemory

Open-source persistent memory runtime for AI coding agents, with hybrid retrieval and zero external dependencies.

Stele

Shared project memory for AI coding agents across Claude Code, Cursor, Codex, and Copilot

Pricing

AgentMemory

Free· Free, open-source (Apache 2.0); bring your own LLM API key

Stele

Freemium· Free tier · from $5.99/mo

Lowest paid tier

AgentMemory

—

Stele

$5.99 / month · Indie

captured 2026-10-28

Free trial

AgentMemory

Not listed

Stele

Yes

API

AgentMemory

Yes

Stele

Yes

Platforms

AgentMemory

cliapi

Stele

—

Open source

AgentMemory

Yes · Apache-2.0

Stele

Not listed

GitHub stars

AgentMemory

29,984

checked 2026-10-29

Stele

—

Last GitHub push

AgentMemory

2026-10-28

Stele

—

First commit

AgentMemory

2026-02

Stele

—

Package downloads (30 d)

AgentMemory

77,138 · npm @agentmemory/agentmemory

checked 2026-11-07

Stele

—

Hacker News stories

AgentMemory

1

checked 2026-11-07

Stele

1

checked 2026-10-21

Earliest Wayback capture

AgentMemory

2026-04-19

earliest archived capture of the site, not a launch date

Stele

2026-07-22

earliest archived capture of the site, not a launch date

Company

AgentMemory

AgentMemory

Stele

—

Model used

AgentMemory

Multi-model (Claude, Gemini, MiniMax, OpenRouter)

Stele

—

Best for

AgentMemory

Pick AgentMemory if you want a drop-in, self-hosted memory layer for your coding agent stack without running a vector DB or graph store.

Stele

Developers and small teams who juggle multiple AI coding agents (Claude Code, Cursor, Codex, Copilot) and want a persistent, shared project memory that survives tool switches and session resets.

Not for

AgentMemory

Skip it if you need a hosted, multi-tenant memory service with SLAs or a production-grade datastore behind it.

Stele

Solo developers who stay inside one agent and one IDE, or enterprises with strict data-residency rules who cannot wait for the self-hosted edition.

Editorial score

AgentMemory

7.3 / 10

Stele

—

Use cases

AgentMemory

agent-memorycoding-agentscontext-managementknowledge-graphmcp-server

Stele

shared memory across AI coding agentscross-tool project context handofftask queue for multi-agent workflowsagent onboarding from an existing codebasetracking failed refactor attemptscoordinating Claude Code and Cursor on one repoMCP-based agent memory backendarchitectural decision log for AI agents

Pros

AgentMemory

• Zero external infrastructure: single Node process, JSON on disk
• Triple-stream retrieval (BM25 + vectors + graph) with sub-20ms recall
• Native plugins for Claude Code, Cursor, Cline, Windsurf, and 15+ agents
• Apache 2.0, runs on your existing LLM subscription
• Strong benchmark numbers (95.2% R@5 on LongMemEval-S)

Stele

• MCP-native, so it works with Claude Code, Cursor, Codex, and Copilot without per-tool adapters
• One-line CLI install with automatic onboarding from an existing repo
• Shared task queue prevents two agents from duplicating the same work
• Graph-based memory captures failed attempts, not just successful ones, so agents stop repeating dead ends
• Free tier is genuinely usable for solo developers (unlimited public projects, one private)
• Self-hosted SQLite edition on the roadmap for teams that need local data
• Export and deletion controls on private project graphs

Cons

AgentMemory

• Pre-1.0 (v0.9.27), expect breaking changes
• Single-process JSON storage may not scale to team-wide deployments
• Self-hosted only; you operate the runtime
• Effectiveness depends on the LLM provider you wire in

Stele

• Currently hosted-only; the promised self-hosted build is not yet shipped
• Value depends on running multiple agents or switching tools often, less compelling for single-agent users
• Shared memory across agents can propagate a bad decision if not curated
• Early-stage product with limited public track record and small community
• Private project quota on the free tier is tight for anyone with several client repos

Website

AgentMemory

agent-memory.dev

Stele

stele-ai.dev

Editorial score: rule-based, 0–10, from AI-assisted profile inputs (see /methodology) — not a user rating; “—” means unscored. “Not listed” means we have no record of it, not that it is absent. GitHub figures and prices carry the date they were checked or captured; prices are shown as published, unconverted.