Code Mode is the point; the UI is just the surface it happens to wear. demo:code and demo:acp-code collapse into one dispatcher (scripts/demo-code-mode.mjs): `pnpm run demo:code-mode [repl|acp]` — repl (default) boots the stdio REPL over examples/code-agent, acp serves examples/acp-agent's code-mode overlay; each UI runs the exact node invocation its standalone script ran, and an unknown argument fails loud with usage. All nine references across READMEs, the RFC, the overlay header, and the keyless-smoke comment renamed. Smoked all three paths: usage exit 2, ACP initialize handshake, REPL boot + EOF.
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:code-mode acp` 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'
|