session-orchestrator vs CommitLore
session-orchestrator is a plugin bundle for AI coding tools published by Kanevry. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). CommitLore is an MCP server published by MongLong0214. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  session-orchestrator |  CommitLore |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.0.0-alpha.14 Forks (GitHub): 7 Stars (GitHub): 53 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 Forks (GitHub): 4 Stars (GitHub): 18 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-orchestrator | CommitLore |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 53 (better) | 18 (worse) |
| Forks (GitHub) (differs) | 7 (better) | 4 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Not stated |
| 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) | 4 | Not published |
| Parts of the bundle (differs) | 25 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kanevry/session-orchestrator | github.com/monglong0214/commitlore |
| 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
session-orchestrator
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.
CommitLore
Git-native decision memory for coding agents: only the decisions still in force for the edited path
How to run each
session-orchestrator As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install session-orchestrator@claude-communityCommitLore
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: session-orchestrator · What it can do: CommitLore · 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 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.