Ext Ops Panel
Open dashboard
Comparison

claude-memory vs Where Was I

claude-memory is a plugin bundle for AI coding tools published by Valentino Stoll. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Where Was I is a plugin bundle for AI coding tools published by sebastianbreguel. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-15. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclaude-memoryWhere Was I
Community marketplace codenamev/claude_memory Listed
Version: 0.13.2
Forks (GitHub): 2
Stars (GitHub): 27
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 2
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

claude-memory vs Where Was I
Factclaude-memoryWhere Was I
Marketplaces that list it11
Stars (GitHub) (differs)27 (better)2 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot 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)94
Parts of the bundle (differs)155
LicenceMITMIT
Repository (differs)github.com/codenamev/claude_memorygithub.com/sebastianbreguel/engram
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

claude-memory

In its own words, on Community GitHub marketplaces:

Long-term memory for Claude Code. Recalls architecture, conventions, and decisions across sessions, plus an episodic observation log of what happened — so Claude explains your codebase without file traversal, follows your patterns, learns from corrections, and never re-asks what it already learned.

Where Was I

In its own words, on Claude Code: claude-plugins-community:

Persistent memory for Claude Code — at ~350 tokens ambient cost, with no Docker, no API keys, and no MCP servers. Engram captures your sessions structurally on PreCompact (zero LLM cost), extracts atomic memories via a single lightweight LLM digest (preferences, practices, current context), and detects emergent patterns from your history — files you always edit together, recurring errors, tool usage anomalies — stored as an auditable Obsidian-compatible wiki. Key features: • Per-project handoff notes — at session start you get a narrative message from the last session in this project • Atomic UPSERT memories keyed by topic — latest wins, no drift, no embeddings • Emergent pattern detection (co-edits, error recurrence, project streaks, tool anomalies) • Durable preferences stay global; ephemeral context is scoped per project • 4-flag CLI surface: --stats, --query, --memories, --forget • Everything local: SQLite at ~/.claude/memory.db, markdown wiki at ~/.claude/patterns/

How to run each

claude-memory As a Claude Code plugin

Claude Code
/plugin marketplace add codenamev/claude_memory
/plugin install claude-memory@claude-memory-marketplace

Where Was I As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install enam@claude-community

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: claude-memory · What it can do: Where Was I · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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