npm / filesystemOfficial
DSH Attachment Local
by DeepSeek
Private content-addressed DSH_HOME attachment storage
CAPABILITY INDEX
Filesystem
08Explore filesystem DSH plugins for controlled file access, search, editing, storage, and structured content operations.
npm / filesystemOfficial
DSH FS Observation Policy
by DeepSeek
File-context policy plugin for the DeepSeek Harness — observed-state, read-before-edit, and version-guarded write/edit added over the ctx.fs provider seam through the fs/* event gate (no service API)
npm / filesystemOfficial
DSH Spill Local
by DeepSeek
Local-filesystem implementation of the DeepSeek Harness spill storage seam (private session-scoped files)
npm / filesystemOfficial
DSH Spill Policy
by DeepSeek
Tool-result spill policy for the DeepSeek Harness — replaces oversized plain-text tool results with a retained preview plus a spill-file path (no service API)
npm / filesystemOfficial
DSH Storage
by DeepSeek
Storage hub (ctx.storage): named backend registry plus mounted data-form facilities for the DeepSeek Harness
npm / filesystemOfficial
DSH Storage Domain
by DeepSeek
Domain data form (ctx.storage.domain): schema-validated, event-emitting KV domains over storage backends for the DeepSeek Harness
npm / filesystemOfficial
DSH Storage JSON
by DeepSeek
JSON file KV storage backend for the DeepSeek Harness storage hub
npm / filesystemOfficial
DSH Tool FS Search
by DeepSeek
Model-facing filesystem discovery tools (glob, grep) backed by the packaged ripgrep binary (@vscode/ripgrep)
DSH CATEGORY GUIDE
How to choose Filesystem DSH plugins
Filesystem DSH plugins give DeepSeek Harness structured access to files, directories, search, storage, and content operations. They may provide simple read and write tools or higher-level persistence layers. The most important differences are path boundaries and how destructive changes are controlled.
Where these plugins help
- Read, write, search, and patch operations
- Project storage and structured persistence
- Safe file boundaries for agent workflows
How to compare
Compare allowed roots, symlink handling, binary file support, encoding, search behavior, atomic writes, backups, deletion rules, and audit output. Prefer plugins that resolve targets explicitly and make overwrite or recursive operations easy to review.
Before you install
Point the plugin at a temporary directory first. Verify behavior for missing files, large trees, symlinks, permission errors, and partial writes. Never grant a broad home or system directory when a project-specific root is sufficient.
FAQ / 02
Frequently asked questions
What permissions should a filesystem plugin receive?
Grant only the project directories and operations required for the task. Separate read access from write or delete access where possible, and avoid broad unresolved paths or personal directories.
Why does symlink handling matter?
A path that appears inside an allowed directory can point elsewhere through a symlink. Plugins should resolve and validate final targets so directory boundaries remain meaningful.