langfuse-observability vs lean-memory
langfuse-observability is a plugin bundle for AI coding tools published by langfuse. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). lean-memory is a plugin bundle for AI coding tools published by lean-memory. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-23. 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
| Marketplace |  langfuse-observability | |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 1.2.0 Forks (GitHub): 48 Stars (GitHub): 29 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 48 Stars (GitHub): 29 Not marked · First seen |
Not listed |
| Community marketplace wuesteon/lean-memory | Not listed | Listed Version: 0.2.1 Forks (GitHub): 40 Stars (GitHub): 43 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
| Fact | langfuse-observability | lean-memory |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 29 (worse) | 43 (better) |
| Forks (GitHub) (differs) | 48 (better) | 40 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (lean-memory-console) |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 2 | 6 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/langfuse/claude-observability-plugin | github.com/wuesteon/lean-memory |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
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
langfuse-observability
Langfuse observability plugin for Claude Code — captures and exports traces, spans, and session telemetry from Claude Code to Langfuse for LLM monitoring, debugging, and evaluation
lean-memory
Observing MCP + read-only console for lean-memory: store and search agent memories from Claude Code, then verify the supersession spine, per-hit score breakdown, and provenance episodes in a local UI.
How to run each
langfuse-observability As a Claude Code plugin
/plugin install langfuse-observability@claude-plugins-officiallean-memory As a Claude Code plugin
/plugin marketplace add wuesteon/lean-memory
/plugin install lean-memory@lean-memory-consoleCommands 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: langfuse-observability · What it can do: lean-memory · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.