KAGENTXINTEL TERMINAL

Agentmemory

The official website positions Agentmemory as a local persistent memory product for AI coding agents, claiming to capture sessions and recall them in subsequent sessions.

Who it is for: Developers using coding agents that support hooks, MCP, or REST API

Positioning

The official website positions Agentmemory as a local persistent memory product for AI coding agents, claiming to capture sessions and recall them in subsequent sessions.

  • Product stage: Public release; the GitHub Releases page shows v0.9.29 as of 2026-08-18.

Core features

  • Automatic Session Capture: The product provides 12 automatically captured hooks, sending session start, prompt, tool call, and session end events into the memory pipeline.
  • Hybrid Retrieval and Version Governance: The official site states that the main retrieval path combines BM25, vector, and knowledge graph scores and re-ranks them on-device; replaced versions do not appear in current retrieval results, but historical records are still queryable.
  • Local Execution: The official website and documentation state that the product runs locally and claims no external database is needed.
  • Session Integration: Official documentation states that after configuring provider key, compression, summarization, integration, and graph extraction are enabled; the official site states that when a session ends, raw observations can be compressed, duplicates merged, outdated records decayed, and audit lines recorded.
  • Session Import and Extraction: The official site states that the product can import Claude Code JSONL sessions, rebuild indexes, and generate session crystals and lessons from them.
  • Multi-Agent Access: GitHub README states that the product can collaborate with agents supporting hooks, MCP, or REST API, allowing different agents to share the same memory server.

Target users

  • Developers using encoding agents that support hooks, MCP, or REST API: The official site positions Agentmemory as a local persistent memory product for AI coding agents, claiming to capture sessions and recall them in subsequent sessions.

Pricing

  • Current data indicates a 'free' signal in the official pricing snapshot; public paid models have not been verified. · Only the 'free' signal can be confirmed; cannot confirm packages, permanent free boundaries, enterprise support, or pay-as-you-go pricing methods.: Whether the actual paying party is an individual developer, team, or enterprise; whether there are hosted versions, enterprise versions, support services, or future charging plans.

Verdict

Verified materials support its positioning as a local persistent memory product for AI coding agents, covering session capture, recall, integration, history import, and multi-interface collaboration; however, independent user feedback, business data, retention, commercialization, and product-market fit evidence are insufficient, so only aPhased judgment at the product mechanism level can be formed currently.

  • Strength: Product positioning and basic value chain are relatively clear: capturing sessions, recalling memories, and reusing them in subsequent sessions. Verified functions cover automatic capture, hybrid retrieval, version governance, local operation, and session integration. Apache-2.0 license, npx installation method, hooks, MCP, and REST access provide signals for public trial and integration.
  • Limitation: Positive feedback consists of only a few cases displayed on the official website; there is a lack of independent user, Reddit, X, and independent evaluation samples. Public Issues reports involve health checks, model requests, graph node identity, and Replay content integrity; the status of fixes and their actual impact on users remain unverified. Price plans, payment boundaries, paying users, revenue, retention, financing, enterprise deployment, and real commercialization data are unknown.

How it delivers value

  • Task Trigger and Input: Session start, prompt, tool call, and session end events enter the memory pipeline. → Session start, prompt, tool call, and session end events enter the memory pipeline.
  • Context Understanding and Retrieval: The system combines BM25, vector, and knowledge graph signals for retrieval, and excludes deprecated versions from the current retrieval results. → The system combines BM25, vector, and knowledge graph signals for retrieval, and excludes deprecated versions from the current retrieval results.
  • Execution and Result Delivery: A GitHub README example states that the next session can know the architecture choices and test coverage of the previous session. → A GitHub README example states that the next session can know the architecture choices and test coverage of the previous session.
  • Feedback and Memory Integration: After configuring the provider key, original observations can be compressed, duplicates merged, and outdated records decayed when the session ends. → After configuring the provider key, original observations can be compressed, duplicates merged, and outdated records decayed when the session ends.
  • Cross-Session and Cross-Client Reuse: The product supports collaboration with different agents through hooks, MCP, or REST API, and shares the same memory server. → The product supports collaboration with different agents through hooks, MCP, or REST API, and shares the same memory server.

Competition

The GitHub README comparison table compares Agentmemory with products like mem0, Letta/MemGPT, Zep/Graphiti, and lists dimensions such as automatic capture, retrieval, external dependencies, and deployment methods; no independent testing was conducted on the same dataset in this round.

  • vs mem0: Wins: The README comparison table lists automatic capture, retrieval, and deployment methods as comparison dimensions; Agentmemory's specific relative advantages still need independent verification. Loses: Relative differences in general memory API, ecosystem, and hosting capabilities are insufficiently supported by evidence in this round.
  • vs Letta / MemGPT: Wins: The README comparison table lists both products' positioning and deployment methods as comparison dimensions; no independent relative conclusion was formed in this round. Loses: Relative differences in full agent runtime capabilities remain unverified in this round.
  • vs Zep / Graphiti: Wins: The README comparison table automatically captures, retrieves, external dependencies, and deployment methods as comparison dimensions; Agentmemory's relative advantages still require independent verification. Loses: Relative adaptability of time knowledge graph capabilities remains untested independently in this round.

Risks

  • Automatic compression, summarization, integration, and graph extraction depend on provider key; related availability, cost, and failure rate still need verification.: Automatic compression, summarization, integration, and graph extraction depend on provider key; related availability, cost, and failure rate still need verification.
  • Historical versions have recorded cross-agent isolation, data loss on restart, graph performance, and compatibility fixes; runtime reliability still requires ongoing verification.: Historical versions have recorded cross-agent isolation, data loss on restart, graph performance, and compatibility fixes; runtime reliability still requires ongoing verification.
  • Native Windows engine setup requires manual operation; agentmemory connect currently does not support native Windows.: Native Windows engine setup requires manual operation; agentmemory connect currently does not support native Windows.
  • Public issue reports on GitHub Issues include health checks, model requests, repeated graph nodes, and Replay content integrity; whether these have been fixed remains to be verified.: Public issue reports on GitHub Issues include health checks, model requests, repeated graph nodes, and Replay content integrity; whether these have been fixed remains to be verified.

Company

  • Stage: Public release; GitHub Releases page shows v0.9.29 as of August 18, 2026.
  • Funding: Not disclosed

User voices

  • Positive: An official website showcase of a Product Hunt launch thread cites a user who filled in a Cursor agent transcript from the past month and found the results "surprisingly accurate."
  • Positive: Another official website showcase of a Product Hunt launch thread cites a user who reported an improved experience after using it for two weeks consecutively.
  • Negative: The GitHub Issues list shows public reports of the /agentmemory/health endpoint returning 503 when checking the health of a process.
  • Negative: The GitHub Issues list shows public reports of duplicate graph nodes, default model compression requests returning 400, and Replay losing original prompt, tool, and response content.
  • Requested: Positive feedback only comes from two case studies in the official website's Product Hunt launch threads, which is insufficient to extrapolate overall satisfaction or retention.
  • Requested: Negative feedback comes from public issue reports on GitHub Issues, which does not equate to the general user experience; whether the issues have been resolved and their actual impact still need verification.
  • Requested: Attributable user samples from Reddit, X, and independent reviews still require targeted collection.

Sources

Updated 2026-08-18

Visit Agentmemory