0 Fork 0

Files

T

imccyu f7d85bf9f5 fix(headless): CI green + review-bot findings for the shared composition

Coverage: api-proxy.ts joins the web-transport exclusion block (its
behavior specs moved here with it; the assembled-entry coverage lands with
the GUI test lane). Static: config-catalog regenerated after the log-round
revert shifted a source anchor. Prose brought current per review: the cli
README now describes the one shared composition (and its build
prerequisite), the apiproxy README points at the api-gateway row instead of
the deleted runtime package, and the config-tree agent note's headless
deferral paragraph records what actually landed (bilingual pair
re-recorded).

2026-07-25 14:40:45 +08:00

src

test(web): real-composition webserver spec

2026-07-25 14:40:45 +08:00

cordis.yml

feat(web): boot dsh web from a config tree via AppCLIEntry

2026-07-25 10:25:02 +08:00

package.json

feat(headless): boot dsh -p from the shared composition; retire dsh-host-runtime

2026-07-25 14:40:45 +08:00

README.md

fix(headless): CI green + review-bot findings for the shared composition

2026-07-25 14:40:45 +08:00

tsconfig.json

test(web): real-composition webserver spec

2026-07-25 14:40:45 +08:00

tsdown.config.ts

feat(cli): dsh CLI with personal config overlays from ~/.config/dsh

2026-07-22 14:29:28 +08:00

README.md

`@deepseek-ai/dsh`

The dsh command-line entry follows the apps/ assembly tier: apps/* are product assemblies over packages/* libraries. Plain dsh [config.yml] boots the interactive TUI coding agent, dsh -p "task" runs one headless turn, and dsh web serves the browser UI.

The TUI surface:

boots the shipped default config (examples/tui-agent/cordis.yml) or an explicit config argument, through dsh-app-boot;
resumes a persisted session with dsh --resume <session-id> and, when the Node host exposes process.execve, supplies the TUI's in-place handoff host: after selector preflight and current-session flush, the host disposes the app and replaces the process with a normalized resume flag; runtimes without process replacement keep the displayed command fallback, the flag still sets RESUME_SESSION_ID before boot, and a missing or unreadable id fails loud instead of creating a fresh session;
treats the invoking directory as the workspace — sessions, relative paths, and workspace instructions resolve from the cwd;
tells the agent where its own source lives: after boot it adds a prompt section naming this harness checkout, resolved from the launcher's real path so it holds under a PATH symlink and an arbitrary cwd, so the self-referential cordis toolset can read and modify it;
applies the personal overlay from ~/.dsh (see app-boot's Personal config): .env fills environment gaps (ambient > project .env > personal .env), config.yaml patches the booted tree.

The Web and headless surfaces boot one shared composition (cordis.yml): both treat the invoking directory as the default project, load applicable AGENTS.md/CLAUDE.md instructions into each agent-loop request prefix with a 65,536-byte render budget, and opt into first-message model titles. Headless differs only in listening on an OS-assigned port (parallel dsh -p runs never collide; the stderr-printed URL opens the live session in a browser). Both need the frontend dist and client bundles built (pnpm run build && pnpm run build:web).

Install (developer machine)

Symlink the source-running launcher onto your PATH; it resolves the checkout through its own real path, so code changes apply on the next launch with no build step:

ln -sf "$(pwd)/bin/dsh" ~/.local/bin/dsh

pnpm run dsh runs the same entry from the repo root and forwards arguments directly, for example pnpm run dsh -p "task". The built form (lib/bin.js, via pnpm run build) boots the same config under plain Node.