English | 中文
Harness uses cordis.yml to describe which plugins an agent loads and the configuration passed to each one. The file composes capabilities; the generated configuration catalog records the fields and defaults each package actually supports, avoiding a second hand-maintained reference.
The repository examples are runnable configurations and the most reliable starting points for a new project:
dsh base plus the tui.cordis.yml overlay combines the DeepSeek model, Bash, filesystem, compaction, subagents, workflows, and the interactive TUI.A minimal configuration is a list of plugin entries:
- id: llm-deepseek
name: '@deepseek-ai/dsh-llm-deepseek'
config:
apiKey: !!js process.env.DEEPSEEK_API_KEY
models:
- deepseek-v4-flash
- id: bash
name: '@deepseek-ai/dsh-bash-local'
- id: agent-loop
name: '@deepseek-ai/dsh-agent-loop'
config:
agents:
- id: main
provider: deepseek-official
model: deepseek-v4-flash
name identifies an npm package or a local module relative to cordis.yml; id gives the plugin instance a stable identity; and config supplies plugin-specific configuration. Set disabled: true to skip an entry temporarily.
- id: local-tool
name: './src/my-tool.ts'
disabled: false
config:
toolName: my_tool
Plugins load in file order. Place plugins that depend on services after the applications or capability plugins that provide them. Missing models, tools, and plugins fail as early as possible instead of being silently ignored.
The TUI composes base.cordis.yml and tui.cordis.yml, then applies one optional patch list. By default that final list is ~/.dsh/config.yaml; dsh --config <path> replaces the personal list with the named overlay. dsh --config-replace <path> instead boots the named file as the complete tree, without shipped or personal layers. dsh web --config <path> adds its overlay after the shared base and Web surface defaults and before Web profile and CLI-flag patches.
A patch replaces a row's entire config value; it does not deep-merge keys. For example, patching llm-deepseek with only config: { thinking: disabled } also removes that row's configured apiKey and baseURL, so restate every key the row must retain.
The Cordis loader evaluates runtime expressions tagged with !!js. Keep API keys and other secrets in the gitignored .env file at the repository root, never in committed configuration.
config:
apiKey: !!js process.env.DEEPSEEK_API_KEY
cwd: !!js process.cwd()
The tag is !!js, not !js.
The generated plugin configuration catalog lists every current field, type, and default. For composition concepts, continue to the architecture and capability interfaces. To create a configuration, copy the closest entry from the examples overview and adapt it.