@deepseek-ai/dsh-capabilities

@deepseek-ai/dsh-capabilities

English | 中文

Generic Agent Profile recipe catalog and composition coordinator. Native subsystems register effect-owned adapters on ctx.capabilities; an adapter projects JSON-safe descriptors and may apply generation-scoped restrictions. Recipe descriptors distinguish whether an implementation is assembleable, currently healthy, selected by the source Profile, and manageable; they may additionally declare immutable model-discoverable members and an explicit Profile-safe primitive configuration contract.

Structured overrides persist in the capabilities Settings namespace: selection, an optional member allowlist, and owner-declared configuration fields. Global Agent values are inherited by every Profile, explicit Profile values override them, and omission falls back to Profile-native values. plan() validates ids, field types, hard dependencies, and exact composition/topology revisions before retaining an immutable dry-run. apply() accepts only that unchanged, unblocked plan. dsh-agent-presets compiles selection and configuration into native Loader patches, while adapters enforce Tool, Skill, MCP, and provider membership when the next standing generation starts.

Adapters may capture private provider configuration through capture(view). The returned non-secret signature participates in generation identity; mount(ctx, entries) installs the captured state before consumers start. Catalog entries preserve effective explicit memberAllowlist ids independently of discovery, including inherited global grants, so a new connection cannot lose a Profile's restrictions.

Model Experience

Indirectly, through selected Profile plugin rows that determine the tools, skills, prompts, and integrations mounted for new Sessions while existing Sessions retain their starting generation.

KV Cache effect

No direct effect. A changed composition can alter a new Session's visible tool schemas or skill catalog and therefore changes its reusable request prefix; running Sessions remain stable.

Known Limitations and Deferred Work

• Top-level Profile recipes — Profile YAML top-level rows and groups are the selectable units; nested rows move with their owning group.
• Declared dependency graph — named providers, optional ctx.get() paths, conflicts, credentials, and soft dependencies require recipe metadata before the planner can reason about them.