Ext Ops Panel
Open dashboard
Comparison

kumi vs orchestrator

kumi is a plugin bundle for AI coding tools published by annavetech. Marketplaces we read that list it: 1 (Community GitHub marketplaces). orchestrator is a plugin bundle for AI coding tools published by DevsForge. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
Marketplacekumiorchestrator
Community marketplace davepoon/buildwithclaude Listed
Version: 1.5.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Community marketplace devsforge/orchestrator Not listed Listed
Version: 0.1.0
Forks (GitHub): 5
Stars (GitHub): 37
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

kumi vs orchestrator
Factkumiorchestrator
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)37 (better)
Forks (GitHub) (differs)0 (worse)5 (better)
Last release (differs)2026-10-16Not 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)124
Parts of the bundle (differs)5030
LicenceMITMIT
Repository (differs)github.com/annavetech/kumigithub.com/devsforge/orchestrator
Changes in the last 7 days (differs)32
First seen (differs)2026-10-152026-10-16

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

kumi

In its own words, on Community GitHub marketplaces:

A coordinated engineering team of named AI specialists that remembers your project between sessions. Call yui to route work, or call any specialist directly: Go (jaan, siim, mart), Angular (liis, kadi, tiiu), iOS (ren, shu, ryo), Python (eero, anu, ivo), React (noa, rui, aki), SQL (saku), NoSQL (remo), architecture for any stack (kai), process management (enn), and DevOps/infra (sora). Each ships as both a skill and a subagent. Bundled hooks capture finished work when a session ends and say at the next session start that saved work exists, and record per-session and per-agent token and time usage. Every specialist follows the same discipline: read context first, make the smallest correct change, verify.

orchestrator

In its own words, on Community GitHub marketplaces:

Autonomous Development Orchestrator for Claude Code. Spec → Plan → Tasks → 100% Working App. Multi-agent pipeline with zero manual intervention.

How to run each

kumi As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install kumi@buildwithclaude

orchestrator As a Claude Code plugin

Claude Code
/plugin marketplace add devsforge/orchestrator
/plugin install orchestrator@devsforge-orchestrator

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: kumi · What it can do: orchestrator · Compare two other plugins

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