Turtle
f290a8b851
`dsh` shipped two config trees that were 43 rows the same: apps/cli/cordis.yml composed web as 74 flat rows, while the TUI booted examples/tui-agent/cordis.yml whose single `@deepseek-ai/dsh-tui-demo` row mounted twelve plugins behind a twenty-key pass-through Config. Neither file was what its location claimed — apps/cli hardcoded the "example" as the product default and the "demo" bundle was the application — and every capability change had to be made twice. - apps/cli/base.cordis.yml holds the 43 shared rows; tui.cordis.yml and web.cordis.yml are patch lists stating only what differs per surface - overlays apply as SIBLING patch lists at one include level, because include patches never cross an include boundary. Precedence: base < surface < (--config | personal ~/.dsh/config.yaml) < launcher flag/profile patches - `--config` now applies an overlay INSTEAD OF the personal one, so a demo or test tree never inherits the user's route; new `--config-replace` boots a file as the entire tree (the old `--config` behaviour). Both survive /resume - vendor/include: index each `insert`ed row as it is added so a later patch can configure or disable it. Upstream built the id index once before the patch loop, leaving every surface-only row — the whole TUI front door — silently unpatchable from user config. Logged as local modification 8 - session identity moves to dsh-agent-loop's CONFIGURED_AGENT_IDENTITIES_KEY; dsh-tui's MAIN_SESSION_ID_KEY is deleted (only the bundle read it) - delete examples/tui-agent, examples/cordis-agent, packages/examples/tui-demo; TUI tests → apps/cli/tests, cordis e2e → packages/cordis/tool-cordis/tests, examples/code-mode survives as an overlay leaf - `dsh web` gains --config, threaded into AppCLIEntry as an extra overlay Three latent defects surfaced and are fixed here: the TUI captured the optional sessionQuery service once at construction and could permanently disable /resume when it won the mount race; the session-store root silently reverted to a project-local ./.sessions; --config-replace was dropped by the resume handoff. Verified by booting each tree through the real Loader (TUI 55 entries, web 75, zero unsettled) rather than reading YAML. All eight terminal snapshots replay byte-identically; 14/14 PTY smoke, 112/112 snapshots, 25/25 doc-sync, hygiene and lint clean.
1.7 KiB
1.7 KiB
快速开始
English | 中文
本指南带你在 5 分钟内跑起一个 Agent。
环境准备
- Node.js ^22.19 或 >= 24
- 通过 Corepack 使用 pnpm 11
- DeepSeek Platform API key
node -v
corepack enable
pnpm -v
第一步：安装并配置 API key
git clone https://github.com/deepseek-harness/deepseek-harness.git
cd deepseek-harness
pnpm install
在仓库根目录创建已被 Git 忽略的 .env：
DEEPSEEK_API_KEY=sk-your-key-here
第二步：运行一个 Headless 任务
运行一个非交互式任务并打印最终回答：
pnpm run demo:headless "summarize the architecture of this workspace"
Headless 运行一个完整的模型/工具轮次，持久化会话，打印结果后退出。需要规范事件流时可使用 --output-format stream-json。
第三步：使用 TUI
启动交互式 coding agent：
pnpm run demo:tui
这个全屏 Agent 可以读写文件、运行命令、分配子任务和跟踪计划。可以尝试：Create hello.js in the current directory, print "Hello from Harness!", and run it。
回头看
headless-agent 使用 @deepseek-ai/dsh-cli-demo app；交互式 dsh surface 则以 apps/cli/base.cordis.yml 叠加 tui.cordis.yml overlay 组合而成，不使用 app 组合包。二者加载同一个 providerless agent spine，并通过各自的 cordis.yml 为对应 surface 选择 DeepSeek 模型和能力插件。