@jcy2387/dsh-dungeon-party
DSH 五智能体地牢队伍编排插件
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:DamonBao/dsh-dungeon-party#cc479dbf478537f1410ab0c82f4e3f40f4a2df75Dungeon Party 以 @jcy2387/dsh-dungeon-party 发布，当前版本为 0.1.13。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Turn complex engineering work into a disciplined five-agent dungeon run.
DSH Dungeon Party is a five-agent orchestration plugin for DeepSeek Harness (DSH). It maps complex work onto a fixed party—1 Tank, 3 DPS, and 1 Healer—and adds the controls needed to make parallel agents safe and auditable: work orders, leases, write scopes, checkpoints, health signals, validation gates, and recovery.
The party can work concurrently, but expensive workspace computation does not fan out unchecked. Fingerprinting and audit scans run through a persistent Worker pool backed by an explicit FIFO queue.
Multi-agent execution is easy to start and hard to control. Without a protocol, agents can duplicate work, overwrite each other, validate stale state, or flood the host with concurrent scans and messages.
Dungeon Party provides a service-enforced coordination layer:
| Slot | Character | Responsibility |
|---|---|---|
| Tank | Aegis | Owns the objective, plans work, assigns tasks, resolves decisions, and accepts the final result. |
| DPS-1 | Pyra | Executes one leased work order inside its declared write scopes. |
| DPS-2 | Nyx | Executes an independent leased work order and reports evidence. |
| DPS-3 | Aster | Executes an independent leased work order and reports evidence. |
| Healer | Lumina | Independently verifies the workspace, handles maintenance, and coordinates recovery. |
Role visibility is not authorization. Every sensitive operation is checked against the actual bound DSH Session.
FORMING → PLANNING → PLAN_REVIEW → EXECUTING → VALIDATING → COMPLETED
│ │
└── stalled ───┤
└→ REPAIR → VALIDATING
┌──────────────────── DSH Session / Commander ────────────────────┐
│ 27 structured tools │
│ │ │
│ ▼ │
│ DungeonService ── event log ──► Session projection ──► Web UI │
│ │ │
│ ├── PartyAgentManager ──► DPS / Healer agent pool │
│ │ + per-run dispatch locks │
│ │ │
│ └── Workspace FIFO ─────► persistent Worker (pool size 1) │
│ fingerprint / audit snapshots │
└──────────────────────────────────────────────────────────────────┘
.npm-cache/**, are excluded from fingerprints by default.dsh plugin --profile web add @jcy2387/dsh-dungeon-party
Stop the currently running Web process, then start the profile again:
dsh web
dsh plugin --profile desktop add @jcy2387/dsh-dungeon-party
Fully quit and reopen DSH Desktop after installing or upgrading. Restarting alone is not enough when you have only rebuilt a local checkout—the profile loads its own installed package copy from $DSH_HOME/profiles/<profile>/node_modules.
On startup, the package synchronizes its bundled preset to:
$DSH_HOME/.agent-presets/dungeon-party
Create a new Session and select 五人本模式 (Dungeon Party) from the preset picker.
npm ci
npm run typecheck
npm test
npm run build
PACKAGE_TGZ="$(npm pack --pack-destination /tmp)"
Install the generated .tgz into every profile that should use it, then restart that profile. For example:
dsh plugin --profile web add --force "/tmp/$PACKAGE_TGZ"
dsh plugin --profile desktop add --force "/tmp/$PACKAGE_TGZ"
telemetry, aggregate, and serial scope-enforcement modes.write, edit, and bash.| Option | Default | Purpose |
|---|---|---|
scopeEnforcementMode | auto | Resolves to the safest available write-scope enforcement mode. |
maxConcurrentDps | 3 | Maximum number of DPS slots that may hold active leases. |
taskLeaseDurationMs | 600000 | Lifetime of a task lease. |
progressCheckpointIntervalMs | 180000 | Expected checkpoint interval for running work. |
maxMissedCheckpoints | 2 | Misses allowed before progress becomes stalled. |
maxRepairRounds | 3 | Maximum repair rounds per task. |
battleResCharges | 1 | DPS resurrection budget. |
commanderBattleResCharges | 1 | Commander rescue budget. |
healerVerificationTimeoutMs | 120000 | Timeout for an approved verification command. |
validationRequired | true | Requires a current passing validation report before completion. |
Default fingerprint exclusions:
.git/**
node_modules/**
.npm-cache/**
lib/**
dist/**
coverage/**
.dsh/dungeon-party/tmp/**
The runtime also supports an explicit childRoute (provider and model) for pinning child agents to a model route registered in DSH settings.
Requirements:
0.1.2-rc.1 (or newer 0.1.x) runtimenpm ci
npm run typecheck
npm test
npm run build
The repository commits lib/ so an installed package is ready to run without compiling. prepublishOnly enforces typecheck → test → build before publication.
Important source areas:
src/service/dungeon-service.ts event-sourced domain model
src/adapters/party-agent-manager.ts agent lifecycle and dispatch
src/adapters/workspace-computation-queue.ts FIFO Worker pool
src/tools/register.ts model-facing tool behavior
src/tools/output-schemas.ts explicit tool output contracts
client/index.tsx Dungeon Party overlay
preset/dungeon-party/ bundled agent preset
The repository includes two GitHub Actions workflows:
main, pull requests, and manual dispatch. It installs with npm ci, type-checks, tests, rebuilds the package, verifies that committed lib/ artifacts are current, and uploads the packed .tgz as a workflow artifact.v<package.json version>, repeats all quality gates, and publishes the package to npm with provenance via OIDC trusted publishing (no long-lived token secret).To enable npm publishing, configure trusted publishing on npmjs.com for @jcy2387/dsh-dungeon-party, authorizing the Release workflow of this repository — no NPM_TOKEN secret is needed. A typical release is:
npm version patch --no-git-tag-version
npm run build
VERSION="$(node -p 'require("./package.json").version')"
git add package.json package-lock.json lib
git commit -m "release: v$VERSION"
git tag "v$VERSION"
git push origin main --tags
Then create and publish a GitHub Release for that tag. The workflow is idempotent: if the npm version is already published, the publish step is skipped. Release artifacts are no longer uploaded to the GitHub Release (npm with provenance is the single distribution channel).
Dependabot checks npm and GitHub Actions dependencies weekly.
The current persistence and dispatch contract is single-process per run:
EVENT_SEQUENCE_CONFLICT or EVENT_ID_CONFLICT; they are not silently merged.The core orchestration, persistence, recovery, validation, Web overlay, explicit tool contracts, and CPU queue are implemented and covered by automated tests. Planned work includes stronger cross-process append coordination, crash-injection compensation, offline message acknowledgement/retry, and richer DAG/history visualization.
For the complete behavioral specification, see docs/dsh-dungeon-party-prd.md.