Tianyi Cui
1be9baeb7b
Boots the acp-agent example through the existing code-mode.cordis.yml overlay (tool surface collapses to run_code + the generated TypeScript SDK, dispatching through the worker-thread runtime), mirroring how demo:code relates to demo:repl on the stdio side. The overlay header and both READMEs now name the demo as a consumer. Smoke: the server answers an ACP initialize handshake with a clean frame on stdout.
31 lines
1.3 KiB
YAML
31 lines
1.3 KiB
YAML
# Code Mode overlay: the live acp-agent tree (./cordis.yml) with two
|
|
# load-time patches — the app entry's config gains `tools: { mode: code }`
|
|
# (the registry offers exactly one wire tool, run_code, plus the generated
|
|
# TypeScript SDK prompt section) and the worker-thread code runtime joins the
|
|
# tree as `ctx.codeRuntime`. The dsh-acp-agent bin boots this file for
|
|
# `pnpm run demo:acp-code` and when the snapshot harness records the
|
|
# code-mode scenarios; DSH_SNAPSHOT=replay swaps it for the sibling
|
|
# code-mode.cordis.snapshot.yml. A config patch REPLACES the entry's whole
|
|
# config, so the base entry's fields are restated verbatim.
|
|
- id: base
|
|
name: '@cordisjs/plugin-include'
|
|
config:
|
|
path: ./cordis.yml
|
|
patches:
|
|
- id: acp-agent
|
|
name: '@deepseek-ai/dsh-acp-agent'
|
|
config:
|
|
model: deepseek-v4-flash
|
|
persistenceRoot: !!js process.env.DSH_SNAPSHOT_SESSIONS_ROOT ?? './.sessions'
|
|
tools:
|
|
mode: code
|
|
persona: |
|
|
You are a coding assistant powered by the {{model}} model. Your working
|
|
directory is {{cwd}}.
|
|
|
|
Verify your work by running the code or tests. Keep answers brief and
|
|
factual.
|
|
- insert:
|
|
- id: code-runtime
|
|
name: '@deepseek-ai/dsh-code-runtime-worker'
|