ensue-auto-memory vs miro
ensue-auto-memory is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
ensue-auto-memory is a plugin bundle for AI coding tools published by christinetyip. No marketplace we read lists it any more. miro is a plugin bundle for AI coding tools published by miroapp. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. 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
| Marketplace |  miro | |
|---|---|---|
| Community marketplace christinetyip/ensue-auto-memory | Removed on 2026-10-22 Version: not stated Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 2.0.0 Forks (GitHub): 24 Stars (GitHub): 164 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 2.0.0 Forks (GitHub): 24 Stars (GitHub): 164 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.3.0 Forks (GitHub): 24 Stars (GitHub): 164 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 | ensue-auto-memoryno longer listed · | miro |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 4 |
| Stars (GitHub) (differs) | 7 | 164 |
| Forks (GitHub) (differs) | 0 | 24 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.miro.com) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 4 | 8 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/christinetyip/ensue-auto-memory | github.com/miroapp/miro-ai |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago, requires a key |
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 ensue-auto-memory
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Personal AI memory layer. Capture decisions, lessons, and context that carry across sessions.
-
AI work memory for Claude Code: brief, capture, recall, handoff, and distill, backed by a local daemon and MCP so decisions, lessons, project context, and wiki pages carry across…
-
Persistent memory recall and lifecycle capture for Codex sessions via EverMe.
-
A Claude Code plugin that adds structured, categorized memory to your projects.
-
Bounded, plain-text project memory with least-recently-used retention.
-
Persistent project memory for Codex through remem MCP and explicit hook activation.
What each says it does
ensue-auto-memory
Automatic persistent memory that saves preferences, corrections, and project context. Works invisibly in the background.
miro
Secure access to Miro boards. Enables AI to read board context, create diagrams, and generate code with enterprise-grade security.
How to run each
ensue-auto-memory
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
miro As a Claude Code plugin
/plugin install miro@claude-plugins-officialCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only miro has a remote endpoint we check. How we check endpoints
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: ensue-auto-memory · What it can do: miro · 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-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.