seek://news/ecosystem-takes-shape
The Plugin Ecosystem Takes Shape: A Survey
TL;DR
The community awesome list now catalogs 200+ plugins across a dozen categories. We surveyed the shape of it while expanding this map from 15 to 53 verified entries: UI and tooling dominate by count, memory and multi-agent are the most inventive fronts, and a plugin market has already emerged to organize the rest.
Expanding this map from 15 entries to 53 meant reading the whole community catalog — 200+ plugins, a dozen categories — and deciding what a verified map owes its readers. This dispatch records what the ecosystem looks like from that altitude.
The counts, honestly
The community list’s own store claims an npm catalog north of 500 packages; the curated list proper runs past 200. Volume, however, is the least interesting number. What matters is the distribution: the long tail is deep but the head is already distinct.
Where the inventiveness is
Three fronts stand out after reading every entry:
Memory is the most contested idea-space. A dozen-plus plugins disagree about what memory is: cited facts over the session log (dsh-memory), cross-agent local vaults (dsh-mnemon), vector-plus-graph retrieval engines (dsh-memoria), automatic distillation into skills (distill). The number of incompatible metaphors is itself the signal — nobody has settled the question yet.
Multi-agent is where architecture shows. DAG planners with parallel workers and reviewing models (dsh-captain), persistent team rooms, cron-driven routine agents. The harness’s “everything is a plugin” seam makes orchestration a mountable layer rather than a fork.
The tail is genuinely playful. A 2005-style parody ad plugin with a deliberately undersized close button is among the most-starred fun entries. Ecosystems that can joke are ecosystems that trust themselves.
Infrastructure eating itself
The most meta development: discovery infrastructure has become its own category. There is a plugin market (dsh-market), an automated radar that scans and test-gates candidates, an agent-side finder that lets your DSH instance search the catalog mid-conversation, and this map. Four different answers to “how do I find plugins” coexisting within the first weeks is not redundancy — it is a distribution layer forming in real time.
How we selected the 53
Our rule stayed the same as V1.0: verify, then admit. Every entry’s URL must answer 200 at build time; squatters and dead links are rejected with evidence. In crowded niches — usage dashboards, balance meters, Feishu bridges — we took the best-in-class representative rather than every entrant, because a map’s value is judgment, not completeness. The full methodology lives on the about page; the entries themselves are on the map.
Official references