Ecosystem and plugins
Write DSH plugins, publish to the market, ship expert templates, negotiate Host compatibility — for plugin authors and platform maintainers.
AgentKit Studio is not a closed app. It runs as a DSH plugin itself, and it exposes the DSH plugin ecosystem, the template ecosystem, and the Host compatibility contract to you.
Four extension surfaces
| Surface | The problem you are solving | Go to |
|---|---|---|
| DSH plugin | Write a plugin package that a DSH host can load | DSH plugin authoring |
| Plugin market | Make your plugin discoverable, or host your own remote index | Plugin market |
| Expert templates | Define experts and expert teams as JSON | Expert templates |
| Host compatibility | Decide whether the current Host can execute Studio capabilities | Host compatibility |
Where it shows up in the product
| Surface | Slot and id | Order | Source |
|---|---|---|---|
| Plugin market | plugins.item / agentkit-dsh-plugin-market | 50 | src/client/dsh/mount.mjs:49 |
| Codex plugins | plugins.item / agentkit-codex-plugin-market | 90 | src/client/dsh/mount.mjs:52 |
| Expert catalog | Inner page of the Agents panel | — | src/client/pages/expert-catalog.mjs |
| Template square | Inner page of the Agents panel | — | src/client/pages/template-square.mjs |
Studio ships no plugin market of its own: the market is the official DSH Plugins page with its Installed and Discover tabs, and the Host's pluginMarket service reads the index. Studio does two things only — add the bundled community index as the default source, and enable the "Custom plugin indexes" and Computer Use bundles by default.
The market is metadata only
Install, enable/disable, update, and uninstall are all executed by the official DSH plugin manager; fetching, validation, caching, search and paging belong to the official pluginMarket service.
Studio writes no profile, makes no compatibility decision and loads no runtime.
Source: src/plugin-market.mjs:1-16, src/host/default-bundles.mjs:1-18.
Three trust boundaries
The easiest way to get ecosystem work wrong is to blur who is allowed to decide what.
| Boundary | Who decides | What must not happen |
|---|---|---|
| Catalog content | An index document may describe which plugins to offer and how to present them | ❌ It must not declare expectedEntries / service / readinessNote — those probes stay curated, otherwise a third-party document could make the adapter call arbitrary Host services |
| Plugin installation | The official DSH plugin manager | ❌ The market must not write profiles or run installers itself |
| Capability probes | The Host | ❌ A remote document must not assert "and it really loaded" |
Source: src/plugin-market.mjs:22-40, src/host/default-bundles.mjs:9-16.
Versions and identity
A Studio plugin presents one identity but carries four version numbers at once:
| Version | Value | Source |
|---|---|---|
| Plugin version | 0.0.16 | package.json#version |
| DSH baseline | 0.2.2-rc.1 | studio.plugin.json#requiredDsh |
| Host API | dsh-native/0.2.2-rc.1 | studio.plugin.json#requiredHostApi |
| Host contract | 1 | studio.plugin.json#requiredHostContract |
The desktop app carries a fifth version (<dsh version>.<YYYYMMDD>.<ordinal>), and it is not the plugin semver.
The full four-dimensional matrix is in version compatibility.
How to read this chapter
DSH plugin authoring
Manifest fields, four capabilities, three contributions, and the pre-publish checklist.
Plugin market
The format: 1 field table, the bundled community index and how it is generated, the request model and the install path.
Expert templates
The team-template/v1 field table, role blueprint constraints, and validation error codes.
Host compatibility
Five capability probes, three feature gates, and the error code you get when admission fails.
Glossary
A few terms recur throughout this chapter; here is the single agreed spelling:
| Term | Code / value | In one line |
|---|---|---|
| Plugin market | plugins.item slot | One row on the official DSH Plugins page, responsible for discovery |
| Bundled community index | assets/plugin-market/index.json | A format: 1 document that ships with the product and is served by the Host |
| Index source | indexes on pluginMarket | Profile-scoped index URLs the Discover page can add and remove |
| Capability probe | expectedEntries / service | Declarable only by built-in rows, used to verify "the Host really loaded it" |
| Team template | agentkit.studio.team-template/v1 | A multi-role definition with kind: "team" |
| Compatibility contract | requiredHostContract: 1 | An integer that increments when the capability surface changes |
Common misconceptions
| Misconception | Reality |
|---|---|
| "Installing the plugin gives me everything the market lists" | The market lists installable packages; availability depends on whether the Host loaded them — see readiness checks |
| "An index can declare anything" | An index declares presentation and installation facts only; Host capability probes stay in the curated list — see Security and trust |
| "Codex plugins and DSH plugins are the same pipeline" | DSH plugins live on the official Plugins page; Codex is a separate plugins/codex-* path with different install targets |
| "A team is just a list of agents" | A team is a kind: "team" template whose roles may only reference immutable templates, never plain agents |
Next
Start with DSH plugin authoring. If you only need an index source, jump to plugin market; if you are shipping a team, go to expert templates.
For Host version mismatches, read host compatibility, then the error codes.