2365b2c54f
Profile bundles are npm packages declaring dsh.patch in their manifest: dsh-base carries the former base.cordis.yml rows as one insert over the empty profile root; dsh-web-app carries the web overlay plus a runtime glue plugin owning what used to be launcher code (frontend dist resolution via frontend-static, the web-surface prompt section, bash runtime variables, the readiness-gated URL line); dsh-headless carries the one-shot runner driving a task turn through the in-process API carrier under the launcher-provided ctx.headlessIo seam.
1.6 KiB
@deepseek-ai/dsh-headless
English | 中文
The dsh one-shot bundle. cordis.patch.yml rides over dsh-base + dsh-web-app: it moves the webserver to an OS-assigned port (parallel runs never collide), silences the URL line, and inserts this package's headless-runner plugin (config {task}). The runner drives one task turn through the in-process API carrier (InProcessApiClient over toFetchHandler(ctx.apiProxy), so the full wire chain — serialization, zod, SSE framing — really runs), aggregates the turn's final assistant text, writes it to stdout, and requests exit (completed → 0, else 1) through the launcher-provided ctx.headlessIo seam. The Web composition stays mounted, so the running session is observable in a browser at the stderr-announced URL. The launcher patches the task text in (dsh --profile headless "task"), and fails loud when a task is given to a profile without this row.
Model Experience
None, as the runner submits the task as an ordinary user message over the shared composition; prompts and tools belong to the base/web bundles.
KV Cache effect
None; the runner adds nothing to the request prefix.
Known Limitations and Deferred Work
- One turn only — the runner anchors on the first message-triggered turn and exits at its end; queued follow-ups and multi-turn tasks are out of scope.
ctx.headlessIois launcher-owned — booting the headless profile outside thedshlauncher fails loud at activation until the host provides the seam.