Session Relay vs Session Steward
Session Relay is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
Session Relay is a plugin bundle for AI coding tools published by Dimitri Hilverda. No marketplace we read lists it any more. Session Steward is an MCP server published by mallikcheripally. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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 |  Session Steward | |
|---|---|---|
| Community marketplace dimitrihilverda/claude-session-relay | Removed on 2026-10-15 Version: 1.2.0 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.12.0 Downloads/month (npm): 241 Downloads/week (npm): 81 Forks (GitHub): 0 Stars (GitHub): 5 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 | Session Relayno longer listed · | Session Steward |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 5 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (session-steward) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 5 | Not published |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/dimitrihilverda/claude-session-relay | github.com/mallikcheripally/session-steward |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
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 Session Relay
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Multi-session awareness for Claude Code. See all active sessions on the same project, get file conflict warnings when two sessions touch the same file, and send messages between…
-
Let local Claude Code sessions talk to each other in natural language.
-
Inter-session communication — session registry, messaging, and coordination between Claude Code sessions
-
Self-hosted relay: agent sessions on different machines share a board, chat and check git conflicts
-
Peer-to-peer communication between Claude Code sessions on the same machine
-
Coordinate parallel Claude Code sessions for complex features. Alpha plans the effort and assigns tasks. Beta and Gamma build in separate terminals. Delta verifies. Each session…
What each says it does
Session Relay
Shared board, messages and git-conflict checks between Claude Code sessions: local on one machine, or across machines via a relay.
Session Steward
Review and safely clean local Codex and Claude Code sessions
How to run each
Session Relay
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Session Steward As a local MCP server: npm package
claude mcp add --transport stdio session-steward -- npx -y session-steward mcpCommands 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: Session Relay · What it can do: Session Steward · 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.