Ext Ops Panel
Open dashboard
Comparison

agent-memory vs cogmemai-memory

cogmemai-memory is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.

agent-memory is a plugin bundle for AI coding tools published by Alireza Rezvani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). cogmemai-memory is a plugin bundle for AI coding tools published by hifriendbot. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceagent-memorycogmemai-memory
Community marketplace alirezarezvani/claude-skills Listed
Version: 2.14.1
Forks (GitHub): 3 978
Stars (GitHub): 28 652
Not marked · First seen
Not listed
Community marketplace hifriendbot/cogmemai-mcp Not listed Removed on 2026-10-22
Version: not stated
Forks (GitHub): 3
Stars (GitHub): 7
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

agent-memory vs cogmemai-memory
Factagent-memorycogmemai-memoryno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)28 6527
Forks (GitHub) (differs)3 9783
Last release (differs)2026-10-23Not published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)3Not published
Parts of the bundle (differs)61
Licence (differs)MITNot stated
Repository (differs)github.com/alirezarezvani/claude-skillsgithub.com/hifriendbot/cogmemai-mcp
Changes in the last 7 days22
First seen (differs)2026-10-142026-10-13

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of cogmemai-memory

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • MCP AutoMem

    Graph-vector memory for AI assistants using FalkorDB and Qdrant

    by verygoodplugins · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • engram

    Persistent memory with session tracking, compaction recovery, and Memory Protocol. Gives Claude a brain that survives across sessions.

    by Gentleman Programming · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • basic-memory

    The bridge between Claude's working memory and Basic Memory's durable knowledge graph — session briefings, pre-compaction checkpoints, and capture reflexes

    by Basic Machines · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Memory

    Active memory writing during conversation, plus manual /memory:consolidate with theme clustering, ground-truth prune, adversarial pass, and machine validator — no…

    by Frad LEE · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • engram io.github.tstockham96/engram

    Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.

    by tstockham96 · MCP server

    Listed on: Official MCP Registry, Claude Code: claude-plugins-community · Describes nearly the same job

  • memory-mcp

    Persistent memory for Claude Code with hot cache instant recall and semantic search. Give your AI assistant a second brain.

    by Michael Denyer · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

agent-memory

In its own words, on Community GitHub marketplaces:

A four-tier memory ladder for Claude Code where promotion is earned by recurrence, not asserted by confidence. L0 raw transcripts are never injected; L1 candidate atoms are gitignored and recalled on lexical relevance per prompt; L2 project context loads each session start; L3 stable persona is always loaded. L1 to L2 needs three distinct sessions spanning two distinct calendar days (a stated claim needs two; a verified claim is the only single-observation path); L2 to L3 needs two projects and thirty days. Two gates refuse rather than guess: a claim altered by the redaction pass never promotes on evidence alone, and a contradicted claim freezes until a human resolves it. Three hooks run the loop unattended and every one fails open. Nothing reaches a committed CLAUDE.md without an explicit human adopt. Ships 5 stdlib scripts, 3 hooks, a cs-memory-curator agent, /cs-memory, a JSON schema, and a 69-check validator. Concept from TencentCloud/TencentDB-Agent-Memory (MIT); no upstream code included.

cogmemai-memory

In its own words, on Community GitHub marketplaces:

Teaches Claude best practices for memory management — when to save, importance scoring, memory types, and session workflows.

How to run each

agent-memory As a Claude Code plugin

Claude Code
/plugin marketplace add alirezarezvani/claude-skills
/plugin install agent-memory@claude-code-skills

cogmemai-memory

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: agent-memory · What it can do: cogmemai-memory · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built