Files
deepseek-harness/packages/extensions
creatixchu 3c3e0583e5 Merge remote-tracking branch 'origin/feat/cua-approval-format' into feat/cua-permission-onboarding
# Conflicts:
#	apps/web/tests/cua-optin.e2e.ts
#	apps/web/tests/expected/plugin-config/official.expected.md
#	apps/web/tests/expected/plugin-manager/live-enabled.expected.md
#	apps/web/tests/expected/plugin-manager/manager.expected.md
#	apps/web/tests/plugin-manager.e2e.ts
#	packages/api/session-controller/README.i18n.yaml
#	packages/client/ui-plugin-manager/README.i18n.yaml
#	packages/client/ui-plugin-manager/src/client/presentation.ts
#	packages/experimental/cua-bundle/README.i18n.yaml
#	packages/experimental/cua-bundle/README.md
#	packages/experimental/cua-bundle/README.zh.md
#	packages/experimental/cua/tests/application-access.spec.ts
2026-10-20 13:13:41 +08:00
..
2026-10-17 15:10:31 +08:00

description, kind
description kind
Runtime API inspection, process-local runners, and historical Cordis cards. package-group

packages/extensions

English | 中文

Summary

The extensions group provides read-only runtime API discovery for agents, process-local runners for programmatic and browser consumers, and historical generated-plugin cards. Creator mode installs persistent plugins through Plugin Manager. Choose a child package for inspection, Host execution, Client execution, or browser controls.

Table of Contents


Packages

Package Role ctx key
tool-cordis Two read-only tools for runtime API discovery 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 panel and historical lifecycle tool cards client face; registers slots


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.