History

Huanqi Cao dc4d2dc868 docs(bash): document the bashEnv hard dependency and dedupe the demo manifest - tool-bash README (both languages) now shows the real four-service inject and attributes the session-persistence contributor to dsh-bash-env. - pwsh-local README names the also-exported ENV_OVERRIDES/ENCODING_PREAMBLE. - agent-spine-demo drops the duplicate bash-env devDependency key.		2026-08-03 20:26:39 +08:00
..
acp-demo	Merge branch 'worktree-llm-dynamic-config' into worktree-llm-web-config	2026-07-30 15:18:26 +08:00
agent-spine-demo	docs(bash): document the bashEnv hard dependency and dedupe the demo manifest	2026-08-03 20:26:39 +08:00
cli-demo	Merge commit 'ecbf75a5e70f662b6420375140cf12eb6bac7860' into worktree/retarget-pr885-20260729	2026-07-29 21:37:43 +08:00
jsonrpc-demo	docs(i18n): resolve follow-up review findings	2026-07-29 18:38:56 +08:00
README.i18n.yaml	fix(rebase): restore consolidated documentation state	2026-07-29 21:16:31 +08:00
README.md	refactor(cli)!: one shared base config with per-surface overlays	2026-07-29 21:15:42 +08:00
README.zh.md	fix(rebase): restore consolidated documentation state	2026-07-29 21:16:31 +08:00

README.md

examples/ — ready-to-run demo bundles

English | 中文

Pre-composed plugin bundles a thin leaf cordis.yml loads instead of assembling the spine and a front door by hand. These are demo / reference packages — the -demo npm suffix marks each one as non-product surface, readable straight off the package name. The runnable leaves under the repo-root examples/ and the Python SDK runtime are the consumers; each is just its swappable backends plus one bundle entry.

Package	npm name	Role
`agent-spine-demo/`	`@deepseek-ai/dsh-agent-spine-demo`	The executor-less/UI-less agent spine as one bundle plugin, with fallback session titles and an opt-in persisted-goal stack
`cli-demo/`	`@deepseek-ai/dsh-cli-demo`	Headless one-shot app: the spine + JSONL persistence + a pre-created `main` agent, with text and DSH-native JSON output
`acp-demo/`	`@deepseek-ai/dsh-acp-demo`	ACP automation server app: the spine + persisted goals + JSONL persistence + the `acp` bridge (no stdout logger), with a boot `bin`
`jsonrpc-demo/`	`@deepseek-ai/dsh-jsonrpc-demo`	Bin-only runtime that boots an external `cordis.yml` for the stdio JSON-RPC SDK client

agent-spine-demo is the shared bundle; cli-demo and acp-demo compose it with headless one-shot and ACP automation front doors, and own their boot bins. The product dsh CLI uses no bundle: its TUI and web surfaces are a shared base.cordis.yml plus one overlay each. jsonrpc-demo mounts no composition of its own — it boots whatever tree the deployment's cordis.yml names, and is what the Python SDK runtime launches.

These are not product API. The spine pieces they bundle live in core/, human/SDK channels and boot glue in ui/, the automation transport in acp/, and swappable backends in their capability groups; a demo bundle just picks one concrete composition of them. Swap or fork one freely.

Do not confuse this group with the repo-root examples/: that directory holds the runnable cordis.yml leaves; this group holds the bundles those leaves load.

The jsonrpc bin/exe names are legacy

jsonrpc-demo renamed like its siblings, but its bin is still dsh-jsonrpc-agent and the single-file executable is still dsh-jsonrpc-agent-pkg (referenced across the Python distribution). Those names are the SDK's runtime-startup surface; they are reconciled when the SDK unifies that startup flow, not by this move.