Host support: DeepSeek Harness (dsh)

Abierto
#2,072 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@michael-wojcik ya está trabajando en esto.

Desde el 15/11/2026.

  • #2073 de @michael-wojcik — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown, shell

Línea de trabajo

Start by reading docs/specs/cline.md and the Cline install script, since the proposal says DSH should follow that pattern; then check how the README lists existing hosts. The work is four pieces: docs/specs/dsh.md, .dsh/INSTALL.md, .dsh/scripts/install-skills.sh, and the README host list, validated with bun run release:validate and bun run plugin:validate. Done means the installer is idempotent, preserves foreign skills, and supports --check and --uninstall, with the preview caveat documented. Wait for a maintainer to accept carrying a preview host before writing code.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Proposal

Add DeepSeek Harness (DSH) as a supported host, following the Cline pattern: a host spec, an install guide, one install script, and README updates. No skill changes and no changes under skills/.

DSH is a native fit for CE's skills-first distribution:

  • It discovers skills as <root>/<name>/SKILL.md directories — the same shape this repository ships.
  • It injects a name/description catalog and loads bodies on demand, so CE's progressive disclosure works unchanged.
  • It honors disable-model-invocation: true natively: manual-only skills cannot be model-invoked, so the installer needs no --include-manual workaround (unlike Cline).
  • It loads the project's AGENTS.md chain, so CE's canonical instruction file is read without a shim.
  • Discovery roots include <project>/.dsh/skills, <project>/.agents/skills, ${DSH_HOME:-~/.dsh}/skills, and ${AGENTS_HOME:-~/.agents}/skills.

DSH is a developer preview; I verified this against the desktop app runtime 0.2.2-rc.3 on 2026-11-15.

Proposed changes

  1. docs/specs/dsh.md — host spec in the same shape as docs/specs/cline.md: last-verified date, sources, discovery paths and precedence, manual-only behavior, instruction files, capability map, preview caveat.
  2. .dsh/INSTALL.md — global and project install, pin a release, local development, check, uninstall.
  3. .dsh/scripts/install-skills.sh — symlinks each skills/<name> directory into the chosen root; CE-owned links only; idempotent; --check and --uninstall; never replaces an existing user skill, fork, or checkout.
  4. README.md — add DSH to the host list and the install options.

Validation

  • Installer tested for global and project installs, idempotent re-runs, foreign-link preservation, --check, and --uninstall.
  • bun run release:validate and bun run plugin:validate pass locally.
  • bun run test result: see PR.

Maintenance

I'll maintain the DSH host docs and installer, and re-verify discovery paths when DSH publishes stable docs. If you'd rather not carry a preview host yet, I'm happy to keep this as an external guide instead.

Optional companion (not part of this PR)

I also maintain dsh-ce, a separate DSH bundle that mounts the same upstream skills through a preset (so the catalog appears only in CE sessions) and adds a native reviewer and session-memory bindings. It is not required for this host support and can be mentioned or omitted as you prefer.


Prepared with DeepSeek Harness (deepseek-flash).

Lenguaje dominante
TypeScript
Estrellas
25.6k
Forks
2.1k
Merge medio
3 h 57 min
PR fusionados (30 d)
170

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de EveryInc/compound-engineering-plugin

Todos los issues de EveryInc/compound-engineering-plugin

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.