The native adapter's route was named deepseek, colliding with pi-ai's catalog provider of the same name, so the two DeepSeek paths could never be mounted side by side. The web settings page needs both configurable at once. Compositions, fixtures, goldens, scaffolding defaults, and docs all move together (pre-release, no shim); TUI/session-query-spill/ missing-credential goldens re-recorded through their keyless refresh modes because provider-name length shifts box padding and spill truncation points.
33 lines
1.2 KiB
YAML
33 lines
1.2 KiB
YAML
# Code Mode keeps the TUI composition while adding the worker runtime and
|
|
# reducing the model-facing registry to the `run_code` transport.
|
|
- id: base
|
|
name: '@cordisjs/plugin-include'
|
|
config:
|
|
path: ./cordis.yml
|
|
patches:
|
|
- id: tui-agent
|
|
name: '@deepseek-ai/dsh-tui-demo'
|
|
config:
|
|
provider: deepseek-official
|
|
model: deepseek-v4-pro
|
|
resumeSessionId: !!js "typeof resumeSessionId === 'string' ? resumeSessionId : undefined"
|
|
persistenceRoot: './.sessions'
|
|
resumeCommand: 'dsh --resume {session}'
|
|
workspaceContext:
|
|
maxBytes: 65536
|
|
tools:
|
|
mode: code
|
|
welcome: 'TUI Code Mode ready. Give it a multi-tool task.'
|
|
ui:
|
|
showReasoning: true
|
|
maxToolOutputLines: 6
|
|
persona: |
|
|
You are a coding agent powered by the {{model}} model.
|
|
|
|
You work by writing TypeScript programs for run_code: batch related
|
|
tool work into one program, loop and branch where it helps, and print
|
|
or return ONLY the findings that matter.
|
|
- insert:
|
|
- id: code-runtime
|
|
name: '@deepseek-ai/dsh-code-runtime-worker'
|