Ext Ops Panel
Open dashboard
Comparison

project-env-config vs session-orchestrator

project-env-config is a plugin bundle for AI coding tools published by ConanXu-math. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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). As of our marketplace pass on 2026-10-30. 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
Marketplaceproject-env-configsession-orchestrator
Claude Code: claude-plugins-community Listed
Version: 495eeda
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.0.0-alpha.14
Forks (GitHub): 7
Stars (GitHub): 52
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

project-env-config vs session-orchestrator
Factproject-env-configsession-orchestrator
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)52 (better)
Forks (GitHub) (differs)0 (worse)7 (better)
Last release (differs)Not published2026-10-29
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)Not published33
Parts of the bundle (differs)Not published80
Licence (differs)Not statedMIT
Repository (differs)github.com/conanxu-math/project-env-configgithub.com/kanevry/session-orchestrator
Changes in the last 7 days (differs)06
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

project-env-config

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

A Claude Code plugin skill that configures development environments for cloned projects.

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.

How to run each

project-env-config As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install project-env-config@claude-community

session-orchestrator As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install session-orchestrator@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: project-env-config · What it can do: session-orchestrator · 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