memory-toolkit vs chat-fork-map
memory-toolkit is a plugin bundle for AI coding tools published by IlyaGorsky. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). chat-fork-map is a plugin bundle for AI coding tools published by jdneo. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). As of our marketplace pass on 2026-10-13. 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 |  memory-toolkit |  chat-fork-map |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.9.12 Forks (GitHub): 2 Stars (GitHub): 13 Not marked · First seen |
Not listed |
| Copilot CLI: github/awesome-copilot | Not listed | Listed Version: 0.0.5 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
| Fact | memory-toolkit | chat-fork-map |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 13 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 2 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs | Installs as a plugin bundle | Installs as a plugin bundle |
| 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) | 6 | Not published |
| Parts of the bundle (differs) | 16 | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/ilyagorsky/memory-toolkit | github.com/jdneo/copilot-chat-map |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
memory-toolkit
Session memory lifecycle for Claude Code. Structured handoffs between sessions, workstreams to switch context without losing it, background watcher (Haiku) that captures decisions and corrections in real time, docs pipeline that routes session findings into .claude/rules/, model recommendations per task, and PreCompact hook to survive context compaction. Works alongside CLAUDE.md and auto-memory — no daemon, no vector DB, no external dependencies. MIT licensed.
chat-fork-map
Maps branching Copilot conversations so parallel follow-up questions and exploration paths from complex tasks or learning can be navigated without losing context. Its visual layout makes breadth-first exploration easier than managing multiple active threads in a traditional conversation list.
How to run each
memory-toolkit As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install memory-toolkit@claude-communitychat-fork-map
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: memory-toolkit · What it can do: chat-fork-map · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.