The install dialog asks the Host to read a spec before installing it: `plugins/inspect` sorts the spec (registry name, absolute path, git address, tarball), asks the registry through `pnpm view` in the profile directory, or reads a directory's package.json, and refuses what would fail with `plugins/inspect-rejected` and a problem the dialog words under the field. A failed pnpm run carries a `kind` classified from how it ended and what pnpm printed, shown as one line with the output folded behind the details. Enabling happens after the fact from the installed screen, which scrolls the list to the first new bundle. Refusals of the moment and the confirmed cancellation are toasts; the run is stopped through the manager's `cancelInstall` and the dialog offers the spec again once the Host confirms. The non-pack dependency group folds by default under its own name. The host config gains `inspectTimeoutMs`; the CLI passes it explicitly.
description, kind
| description | kind |
|---|---|
| The extensions group map: model-facing tools and dual-half runners for defining, running, and removing dynamic Cordis packages, for users and maintainers navigating the group. | package-group |
packages/extensions
English | 中文
Summary
The extensions group lets an agent inspect and modify the live DSH runtime without editing repository files or configuration. It can define, run, update, stop, and remove dynamic Cordis packages from model tools or a browser panel. A package may affect the host, browser, or both, and immutable versions support controlled updates. Definitions exist only in process memory and disappear when DSH restarts. Choose the child package for model tooling, host execution, browser execution, or browser controls.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
tool-cordis |
Seven model-facing tools: inspect the live runtime, define, run, stop, and remove dynamic packages | registers on ctx.tools |
cordis-host-runner |
Host half: definition registry, sandboxed host-half lifecycle, and the inspect registry that answers browser queries | provides ctx.dynamicCordisRunner and ctx.cordisInspect |
cordis-client-runner |
Browser half: evaluates a browser-half source into a live plugin and answers run requests | client face; provides browser ctx.dynamicCordisRunner |
ui-cordis |
Browser surfaces: the frame-wide panel, lifecycle tool cards, and the @pluginId input source |
client face; registers slots |
Related documentation
- Extensions subsystem — the generated
ctx.cordisInspectandctx.dynamicCordisRunnerservice API. - Generated tool catalog — the seven model-facing tool schemas.
- Generated configuration catalog — the runner's accepted config fields.
- Self-referential Cordis toolset Agent Note — design home for sandbox semantics, lifecycle, and composition.
- Client shells and dynamic packages Agent Note — package placement and build faces for the client halves.
Dev Note
Working context for maintainers — click to expand
The two browser-half packages live in this group rather than under packages/client/ because they are halves of this subsystem's dual-half packages; the client face compiles them through the client program, while the host program references only the host runner.