Yichen Jiang
3a37ec4974
The shipped surface stopped being two yml files: `base.cordis.yml` and `web.cordis.yml` are bundle patch layers now, applied over an empty preset root. This test still opened the old paths, so it failed before asserting anything. It composes the same two layers the profile boot composes, over the same empty root, and heals the flat module fallback the way the boot does — the root lives outside this workspace, so bare plugin names have no other way to resolve. The web bundle's runtime row is disabled beside the webserver: it injects `httpServer`, so a disabled port leaves it pending forever. It owns dist serving and the URL prompt line, neither of which decides an agent's capabilities. `apps/cli` declares the packages the shipped agent presets name again. The bundle split emptied its plugin dependencies, and the flat fallback links only the app's dependency closure — so a preset row naming `dsh-persona` resolved to nothing, and every preset mount failed. Which packages the shipped presets compose is not implied by any bundle: the presets live beside this app's config, so this app is what has to declare them.
@deepseek-ai/dsh
English | 中文
The dsh command is the product launcher for profiles: ordered stacks of plugin-bundle patch layers under the user's own overrides. src/args.ts owns the command grammar, and src/bin.ts loads only the selected runner. Invalid commands, options from another mode, configuration errors, and boot failures exit nonzero.
Entry modes
| Command | Purpose |
|---|---|
dsh --profile <name> |
Boot the named profile under $DSH_HOME/profiles/<name>. |
dsh --profile headless "task" |
Run one fresh persisted session, print the final answer, and exit. |
dsh web |
Alias of --profile web with the Web flag family (--host, --port, --dev, ...). |
dsh plugin --profile <name> <pnpm args> |
Manage a profile's plugins by forwarding to pnpm in the profile directory. |
The invoking directory is the default workspace root. The web and headless profiles auto-initialize on first use from shipped templates; any other profile must be created through dsh plugin.
Profiles
A profile directory holds a package.json (out-of-tree plugin dependencies plus the profile manifest dsh.profile with its ordered bundles list) and a cordis.patch.yml (the user's own patch layer, hot-reloaded on long-lived surfaces). The tree composes over an empty root: each bundle's patch in dsh.profile.bundles order, then the profile's cordis.patch.yml, then the home-level $DSH_HOME/cordis.patch.yml, then --patch overlays, then flag patches. Bundles named in dsh.profile.bundles resolve from the dsh installation first (@deepseek-ai/dsh-base, @deepseek-ai/dsh-web-app, @deepseek-ai/dsh-headless), then from the profile's own node_modules, where pnpm installs out-of-tree plugins. Use --dump-default-config and --dump-config to inspect the composed tree without booting it.
The CLI behavior reference owns exact layer precedence, flags, shutdown behavior, deployment defaults, and the source launcher.
Development
Production runs require built package and frontend artifacts. From a checkout, pnpm run dsh runs the TypeScript entry and forwards arguments; the source-launcher reference describes the PATH symlink and module-resolution contract.