Ext Ops Panel
Open dashboard
Comparison

Talamus vs leteo

Talamus is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

leteo is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.

Talamus is a plugin bundle for AI coding tools published by Ampres. No marketplace we read lists it any more. leteo is a plugin bundle for AI coding tools published by Alexis Sanabria Lopez. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-17. 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
MarketplaceTalamusleteo
Community marketplace ampres-ai/talamus Removed on 2026-10-18
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Community marketplace asanabrial/leteo Not listed Removed on 2026-10-17
Version: 0.3.0
Forks (GitHub): 1
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

Talamus vs leteo
FactTalamusno longer listed · leteono longer listed ·
Marketplaces that list it00
Stars (GitHub) (differs)32
Forks (GitHub) (differs)01
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)Not published5
Parts of the bundle (differs)16
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/ampres-ai/talamusgithub.com/asanabrial/leteo
Changes in the last 7 days44
First seen2026-10-132026-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 Talamus

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

  • claude-code-plugin-for-goodmem-a-memory-infra-for-agents

    With this plugin, you can operate Goodmem's memory infra in plain English, to create, manage, and orchestrate embedders, rerankers, and LLMs, to ingest and create memories from…

    by PAIR-Systems-Inc · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · 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

  • aide-memory

    Persistent memory layer for AI coding agents — your agent remembers what you taught it.

    by aide-memory · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • yggdrasil io.github.VonderVuflya/yggdrasil

    One shared, durable memory for your AI coding agents — local-first, zero-dependency.

    by VonderVuflya · MCP server

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

  • Mindtrail

    Persistent, local-first memory for AI coding agents. Remember, recall and forget across sessions.

    by RohitDeshmukh-1 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • hivemind

    Persistent shared memory powered by Deeplake — captures all session activity and provides cross-session, cross-agent memory search

    by Activeloop · Plugin bundle

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

Its card, with similar plugins by marketplace

What to use instead of leteo

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

  • 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

  • hivemind

    Persistent shared memory powered by Deeplake — captures all session activity and provides cross-session, cross-agent memory search

    by Activeloop · Plugin bundle

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

  • kairn

    Local memory with full-text recall and a recall-and-save skill.

    by PrimeLine · Plugin bundle

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

  • anamnese-core

    Secure, portable, cloud-persistent memory across every conversation. Store and retrieve your personal facts, decisions, tasks, goals, and notes. Accessible from any AI client…

    by AnamneseAI · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • 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

  • 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

Its card, with similar plugins by marketplace

What each says it does

Talamus

In its own words, on Community GitHub marketplaces:

Durable, local-first agent memory with cited recall, provenance, and a consent-aware CLI-first Cursor workflow.

leteo

In its own words, on Community GitHub marketplaces:

Persistent memory with session tracking, compaction recovery, and a save protocol. Gives the agent a memory that survives across sessions.

How to run each

Talamus

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

leteo

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: Talamus · What it can do: leteo · 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