Ext Ops Panel
Open dashboard
Comparison

session-orchestrator vs session-handoff

session-orchestrator is a plugin bundle for AI coding tools published by Kanevry. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). session-handoff is a plugin bundle for AI coding tools published by mehmeteminduran. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-26. 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

Where each is published
Marketplacesession-orchestratorsession-handoff
Claude Code: claude-plugins-community Listed
Version: 2.0.0-alpha.14
Forks (GitHub): 7
Stars (GitHub): 52
Not marked · First seen
Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

session-orchestrator vs session-handoff
Factsession-orchestratorsession-handoff
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)52 (better)0 (worse)
Forks (GitHub) (differs)7 (better)0 (worse)
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)331
Parts of the bundle (differs)793
LicenceMITMIT
Repository (differs)github.com/kanevry/session-orchestratorgithub.com/mehmeteminduran/claude-session-handoff-plugin
Changes in the last 7 days (differs)30
First seen2026-10-112026-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

session-orchestrator

In its own words, on Claude Code: claude-plugins-community:

Session-level orchestration for Claude Code - structures development work into 5 typed waves (Discovery → Core → Polish → Quality → Finalization) with parallel subagent execution, inter-wave quality gates, and verified close-out. Auto-detects GitLab or GitHub from your git remote for full VCS lifecycle support. Three commands replace manual session management: /session starts with project analysis, /go executes the wave plan, /close verifies and commits.

session-handoff

In its own words, on Claude Code: claude-plugins-community:

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 decisions, dead-ends, or "what to do next." Sessions are named, so multiple parallel threads of work can coexist in the same repo. Ships: /handoff [session] — write the current session's state into HANDOFF.<session>.md /resume [session] — read that file, reconcile with git status, and execute the next concrete step A PreCompact hook that blocks context compaction until a fresh handoff exists, so Claude Code never silently summarizes away your unsaved state

How to run each

session-orchestrator As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install session-orchestrator@claude-community

session-handoff As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install session-handoff@claude-community

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: session-orchestrator · What it can do: session-handoff · 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 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