dsh-file-manager
DeepSeek Harness 的文件管理器：右侧可调整大小的文件树（展开/折叠、递归文件名搜索，支持按类型预览 markdown/html/pdf/图像/视频/音频/代码，并可在面板内编辑），带有右键上下文菜单（预览 / 编辑 / 复制路径 / downlo
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-file-manager@0.1.3File Manager 以 dsh-file-manager 发布，当前版本为 0.1.3。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A File Manager for DeepSeek Harness. Adds a resizable file/folder panel on the right side of the page with recursive filename search, per-type preview, inline editing, and a full right-click context menu for files and folders.
Docs in other languages: Tiếng Việt
dsh plugin add with no repo edits and no changes to closed RPCs.
/plugins/file-manager/* routes on ctx.webServer..git, node_modules, dist, .dsh; caps results).# From a local folder or an npm package:
dsh plugin --profile web add /path/to/dsh-file-manager
# or from npm:
dsh plugin --profile web add dsh-file-manager
dsh plugin add pnpm-installs the package into the profile and reconciles it into the profile's bundle list. Restart the harness for it to take effect.
Requires VS Code
codeon PATH for "Open in VS Code"; if missing, that item reports an error but everything else still works.
dsh-file-manager/
├── package.json # dual-face: dsh.bundle.patch (host bundle) + dsh.client (web client)
├── cordis.patch.yml # - insert: [{id: file-manager, name: dsh-file-manager}]
├── lib/
│ ├── index.js # HOST HALF (prebuilt) — /plugins/file-manager/* routes
│ └── client.js # CLIENT HALF (prebuilt bundle) — __ModuleLoader__.load + React
└── README.md
lib/index.js)inject: ['fs']. Registers routes (preferably via ctx.get('webServer') ?? ctx.get('httpServer')):
| Route | Method | Description |
|---|---|---|
/plugins/file-manager/list | GET ?path= | List one directory level, sorted |
/plugins/file-manager/search | GET ?root=&q= | Recursive filename search, skips dense dirs |
/plugins/file-manager/read | GET ?path= | Read text (up to 1 MB) |
/plugins/file-manager/raw | GET ?path= | Stream arbitrary binary with correct MIME (pdf/html/image/video/audio) |
/plugins/file-manager/download | GET ?path= | Download as attachment |
/plugins/file-manager/write | POST | Create-or-replace a file |
/plugins/file-manager/rename | POST | Rename / move |
/plugins/file-manager/delete | POST | Recursive delete file/folder |
/plugins/file-manager/mkdir | POST | Create directory |
/plugins/file-manager/touch | POST | Create empty file |
/plugins/file-manager/open | POST | Open with the default OS app |
/plugins/file-manager/reveal | POST | Reveal in the parent folder (OS app) |
/plugins/file-manager/open-vscode | POST | Open in VS Code (code) |
Reads/writes go through ctx.fs (respects the provider/sandbox). Rename/delete/mkdir/touch/open are operations ctx.fs intentionally does not expose, so they use node:fs on paths the host owns (the client never joins path segments itself).
lib/client.js)Prebuilt bundle following the contract window.__ModuleLoader__.load({id, factory}), require('react'), createElement (no JSX), and self-injected CSS. Registers:
slots.inject('shell.overlay', () => slots.register(
{ name: 'shell.overlay', id: 'file-manager', order: 90, label: 'file-manager' },
(props) => react.createElement(ExplorerPanel, props),
));
slots.inject('conversation.session.header.actions', () => slots.register(
{ name: 'conversation.session.header.actions', id: 'file-manager-toggle', order: 30, label: 'file-manager' },
(props) => react.createElement(ToggleButton, props),
));
The root is derived from the active workspace via the framework hooks (props.useWorkspaces / props.useSessions) and re-roots when the workspace changes.
mountRoot config to the host half and gate paths against it.lib/client.js.lib/client.js is currently a hand-authored prebuilt bundle. To build from TSX with the DSH pipeline, follow packages/client/tsdown.client.ts (clientBundle(...)) and export ./client => lib/client.js./plugins/file-manager/* routes from the origin / (the web server it was loaded from). The host half trusts the same connection fence as the GUI.dsh process. Only install it in deployments you trust; exposing it remotely (--host) is discouraged because of the shared RCE surface.node_modules, dist, .git) are skipped during search to avoid hangs on huge trees.