lijian-ui/dsh-file-manager

dsh-file-manager is a native DSH plugin that targets the DeepSeek Harness desktop shell (dsh web) exclusively, adding two right-side panels — an Explorer and a Preview — alongside an @ file-reference pipeline inside the composer. The Explorer ships Files and Changes tabs backed by the real filesystem and real git; file lookup is debounced at 150ms, while the SCM view parses git status -z porcelain v1 output and supports stage, unstage, and discard (untracked → delete, tracked → restore) with batch-confirm and double-confirm dialogs. The Preview panel is multi-tab and renders markdown, html, code, diff, csv, pdf, word, excel, ppt, image, text, and url with a source/preview toggle, persistent split-editing ratio, mtime-aware save, mid-click close, and right-click batch close, plus an offline Mermaid runtime bundled into the plugin. The @ trigger opens a pi-desktop-style tree multi-select modal that emits native DSH reference chips carrying a hidden payload serialized to @<relative-path>:<lines> on submit, including full-file line-count ranges and selection-derived start–end ranges.

A typical session looks like this: install with dsh plugin --profile web add @lijian-ui/dsh-file-manager (or dsh plugin --profile web add link:$(pwd) after cloning), restart dsh web, open a project, and observe the new column tracks appended to the shell's 3-column grid; type @ in the composer to surface the file picker, drag any Explorer row to insert a relative-path chip, or select code in the preview and click Add to chat to inject a line-bounded chip instead. The same package is also developed against dsh-desktop through a local node_modules/@lijian-ui/dsh-file-manager → extensions/file-manager symlink, so contributors editing source must run npm run build to regenerate lib/ AND restart the dev shell — neither step alone is sufficient. The plugin targets DSH users who want first-class filesystem browsing, live git awareness, and structured file/code references attached to prompts without leaving the chat surface.

Dependencies and limits: the host half is a cordis plugin exposing /filemgr/* routes guarded by a realpath-normalized workspace gate that is loopback-only, with text reads capped at 80k characters and images returned as data URLs; the browser half is framework-free in the core (store, drag engine, layout controller) and React-only in panel components, with chip styles overriding [data-decoration="chip"] globally. Build is npm install && npm run build (tsc -b + tsdown → lib/) followed by npm run test (vitest); the plugin keeps per-project preferences and a master switch in Settings → Web UI plugins, ships dark/light themes, and ships Apache-2.0 attribution to the reference FileManager project. First-run caveats include the strict "edit + build + restart" workflow and the workspace-gate restriction, which means non-loopback HTTP clients will be rejected by design.