e8f5c0b51b
Minimal Electron shell over the DSH JSON-RPC runtime — a first-look at what a ChatGPT.app-style host on top of the DeepSeek Harness looks like, with the harness's normally-invisible internals (trace timeline, context surface, subagent tree, compaction, plugin registry, rubrics) brought forward as first-class UI surfaces so plugin authors and researchers can see what the agent is actually doing. Runs against three keyless-to-live profiles (stdio-echo works on master out of the box; daemon-echo / daemon-vibe-echo activate once the daemon-demo lands; stdio-deepseek and daemon-vibe hit the real DeepSeek API when you supply a key). HARNESS_DEV auto-resolves to the in-repo runtime when this shell ships under examples/desktop/, so a fresh clone launches without config; env DSH_DEV_ROOT overrides for custom layouts, and a sibling deepseek-harness-dev/ checkout is the original dev workflow. Cold-clone gate (P0 fixes for first-time-clone usability): - HARNESS_DEV: 3-candidate resolver (env → walk-up in-repo marker → sibling), unit-tested via mock fs so ordering is locked without needing either real layout on disk. - config yml leaves rewritten at assemble time so the sibling-clone paths (../../deepseek-harness-dev/examples/echo-agent/…) become the in-repo paths (../../echo-agent/…) in the released tree — source yml stays usable for local dev, released tree ships a working shape. - pnpm-workspace.yaml allowBuilds.electron = true (was placeholder). - missing-key card in stdio-deepseek offers a one-click switch to stdio-echo (the keyless profile that works on master) rather than daemon-echo (blocked on the not-yet-shipped daemon-demo). - assemble-oss-release.sh rewrites the source-side breadcrumb name 'dsh-desktop-demo' → 'dsh-desktop' for the released package.json. FOUC guard on the onboarding gate (41fc5df carried) keeps the first-launch splash from flashing before the runtime probe finishes. Test suite (1634 tests in source, 3990 in the runtime repo) covers resolver ordering, renderer classifiers, trace timeline shape, compaction diff rendering, rubric parity, and the missing-key onboarding paths.
60 lines
2.3 KiB
YAML
60 lines
2.3 KiB
YAML
# Vibe leaf: the daemon-echo agent bundle + the self-referential cordis
|
|
# toolset, so a chat inside the shell can inspect + mount plugins into the
|
|
# live runtime. Loaded through the same daemon-demo bin as `daemon-echo.yml`;
|
|
# the sole difference is the extra `tool-cordis` entry at the end.
|
|
#
|
|
# This leaf expects a real model (`mock-echo` cannot compose plugins), so the
|
|
# UI hides the entry point in the mock profile. The real-model shape lives at
|
|
# `examples/cordis-agent/cordis.yml` in the DSH runtime checkout — this
|
|
# leaf's overlays swap in the DeepSeek adapter when the shell is running
|
|
# under the deepseek profile.
|
|
#
|
|
# See packages/cordis/tool-cordis/README.md for the tool trust stance:
|
|
# `cordis_mount` evaluates model-written JS in a node:vm sandbox — grant it
|
|
# like bash access.
|
|
|
|
- id: mock-llm
|
|
name: '../../echo-agent/src/mock-llm.ts'
|
|
|
|
- id: echo-tool
|
|
name: '../../echo-agent/src/echo-tool.ts'
|
|
|
|
- id: bash
|
|
name: '@deepseek-ai/dsh-bash-local'
|
|
|
|
# ctx.fs / ctx.web providers so plugins the model writes have real capabilities
|
|
# to build on. Model-facing read/write/edit + search/fetch tools stay off on
|
|
# purpose — the point is the agent *authors* its own tools rather than picking
|
|
# from a prepacked shelf.
|
|
- id: fs-local
|
|
name: '@deepseek-ai/dsh-fs-local'
|
|
config:
|
|
cwd: !!js process.cwd()
|
|
|
|
- id: web
|
|
name: '@deepseek-ai/dsh-web'
|
|
|
|
- id: web-fetch-local
|
|
name: '@deepseek-ai/dsh-web-fetch-local'
|
|
|
|
- id: session-query
|
|
name: '@deepseek-ai/dsh-session-query'
|
|
|
|
- id: daemon-agent
|
|
name: '@deepseek-ai/dsh-daemon-demo'
|
|
config:
|
|
socketPath: !!js process.env.DSH_DAEMON_SOCKET_PATH
|
|
lockfilePath: !!js process.env.DSH_DAEMON_LOCKFILE_PATH
|
|
persistenceRoot: !!js process.env.DSH_DAEMON_SESSIONS_ROOT ?? './.sessions'
|
|
persona: |
|
|
You are the DSH vibe agent: you author cordis plugins to extend your own
|
|
runtime. Use cordis_inspect to look around (its `api` and `events`
|
|
sections are your reference), cordis_mount to add plugins, and
|
|
cordis_unmount to clean up. In mounted code, never use Node built-ins
|
|
(require/setTimeout/fetch) — use the cordis services via inject: fs,
|
|
web, bash, timer (ctx.setTimeout). Prefer small single-purpose plugins.
|
|
|
|
# Loaded last so ctx.tools exists — the cordis toolset registers into it.
|
|
- id: tool-cordis
|
|
name: '@deepseek-ai/dsh-tool-cordis'
|