persistent-handoff vs Silent Door Repository Handoff Planner
persistent-handoff is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
persistent-handoff is a plugin bundle for AI coding tools published by adrrr. No marketplace we read lists it any more. Silent Door Repository Handoff Planner is an MCP server published by silent.aibitious.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 | ||
|---|---|---|
| Community marketplace adrrr/persistent-handoff | Removed on 2026-10-19 Version: 0.3.1 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.5.0 No figure published 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 | persistent-handoffno longer listed · | Silent Door Repository Handoff Planner |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (silent.aibitious.com/mcp) |
| 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) | 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/adrrr/persistent-handoff | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 43 h ago returned HTTP 405 |
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 persistent-handoff
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Writes a handoff document when a session has sat idle long enough that its prompt cache is about to go cold.
-
Compact the current conversation into a handoff document for another agent to pick up. Configurable save location, redaction enforcement, SessionStart auto-load + SessionEnd…
-
Creates comprehensive handoff documents for seamless AI agent session transfers. Use when context window approaches capacity or work session is ending.
-
Push AI session handoffs to HandoffKit automatically via MCP. Store your AI prompts, handoff messages, and session context in one place. Checkbox-select what each session needs…
-
Turns what you teach Claude into project notes, catches its usual slips, keeps the cache warm while you're away, and picks long sessions back up
-
A Claude Code plugin that lets you hand off an in-flight task from one AI tool to another — Claude Code → Codex, Codex → Cursor, Cursor → a fresh Claude session — without losing…
What each says it does
persistent-handoff
A handoff file that outlives the session that wrote it: one file per agent, updated at milestones, read back automatically at every session start.
Silent Door Repository Handoff Planner
Choose files for an agent handoff using filename decisions. No file contents or credentials.
How to run each
persistent-handoff
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Silent Door Repository Handoff Planner As a remote MCP server
claude mcp add --transport http repository-safety-preflight https://silent.aibitious.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Silent Door Repository Handoff Planner 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: persistent-handoff · What it can do: Silent Door Repository Handoff Planner · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.