0 Fork 0

Files

T

Turtle f290a8b851 refactor(cli)!: one shared base config with per-surface overlays

`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.

2026-07-29 21:15:42 +08:00

1.7 KiB

Raw Blame History

Quick start

English | 中文

This guide gets an agent running in five minutes.

Prerequisites

Node.js ^22.19 or >= 24
pnpm 11 through Corepack
A DeepSeek Platform API key

node -v
corepack enable
pnpm -v

Step 1: install and configure the API key

git clone https://github.com/deepseek-harness/deepseek-harness.git
cd deepseek-harness
pnpm install

Create the gitignored repository-root .env:

DEEPSEEK_API_KEY=sk-your-key-here

Step 2: run one Headless task

Run a non-interactive task and print its final answer:

pnpm run demo:headless "summarize the architecture of this workspace"

Headless runs one complete model/tool turn, persists the session, prints the result, and exits. Use --output-format stream-json when you need the canonical event stream.

Step 3: use the TUI

Start the interactive coding agent:

pnpm run demo:tui

The full-screen agent can read and write files, run commands, delegate subtasks, and track a plan. Try: Create hello.js in the current directory, print "Hello from Harness!", and run it.

What happened

headless-agent uses the @deepseek-ai/dsh-cli-demo app; the interactive dsh surface instead composes apps/cli/base.cordis.yml with the tui.cordis.yml overlay and no app bundle. Both load the same providerless agent spine, while their cordis.yml files select the DeepSeek model and capability plugins appropriate to each surface.

Next steps

Configuration — understand the cordis.yml format
Develop a plugin — build your own tool or backend

1.7 KiB Raw Blame History