drive9-ai/drive9-dsh
Drive9 for DeepSeek Harness is a standard DSH bundle giving agents persistent workspaces and durable, bounded tool evidence: a Drive9 revision-CAS filesystem backs the read/write/edit tools, an isolated evidence backend stores oversized tool results, model-visible result_search and result_read tools enforce hard output limits, and the mount lifecycle stays separate from the harness runtime so evidence survives after a runtime or workspace disappears.
Drive9 for DeepSeek Harness provides persistent agent workspaces and durable, bounded tool evidence. Four independent Cordis components make it up: a Drive9 revision-CAS filesystem backing the harness's read, write and edit tools; an isolated evidence backend for oversized tool results; model-visible result_search and result_read tools with hard output limits; and a model-visible runtime-context warning for the opt-in eventual mount profile. The architecture keeps four lifecycles separate - the agent loop and session history belong to DeepSeek Harness, the persistent workspace and immutable evidence belong to Drive9, and the shell, sandbox, language servers and compute runtime belong to the user's DSH deployment. The Drive9 mount exposes only the persistent workspace inside an existing runtime and does not own that runtime, while evidence remains readable after the runtime or workspace disappears because it is stored under a separate, unmounted Drive9 root.
Install
dsh plugin --profile web add @drive9/drive9-dshCopied verbatim from the README's install block; the README also documents a tarball install dsh plugin --profile web add "$PWD/$PACKAGE_TARBALL" and removal with dsh plugin --profile web remove @drive9/drive9-dsh.
Compatibility
A standard DSH bundle with four independent Cordis components. The default strong mount-consistency profile requires a Linux Drive9 FUSE mount in the same execution world as the harness process tools, proving SDK-to-mount and mount-to-SDK coherence at startup; the opt-in eventual WebDAV profile may let process tools observe stale mounted bytes for more than 30 seconds after an SDK write. The integration never silently downgrades strong to eventual. English README.
Details
- Repo: drive9-ai/drive9-dsh
- Category: Coding & Development
- Stars: 2
- Version: GitHub repo drive9-ai/drive9-dsh (2★); npm package @drive9/drive9-dsh at 0.1.0 (registry check 2026-10-13; the registry repository field resolves back to this repo).
Alternatives
030611/dsh-context-provenance · 030611/qiushi-dsh-evidence-audit · 0x3fffff/dsh-desktop-launcher