dsh-file-explorer

A DeepSeek Harness Web GUI plugin that shows a file directory tree in the left workspace area.

What it adds

• A 文件目录 / File Explorer toggle button at the bottom of the left sidebar (sidebar.footer.action).
• A bottom-anchored card that slides up the left sidebar (non-linear easing):
  • half-height by default (just past the middle); a top bar with a full-expand button covers the whole sidebar, plus restore and close;
  • tree browsing: click a row's arrow to expand/collapse subdirectories inline, double-click a folder name to enter it, single-click a file to open it with the host OS;
  • a drive-selection page ("此电脑") — "up" from any drive root lands there, so you can switch disks;
  • a full interactive breadcrumb path chain (wheel-scrollable when it overflows), plus home / up / path editing / refresh / show-hidden / follow-session;
  • clicking the blank sidebar area above the half card collapses it;
  • the card's right edge tracks the sidebar column (ResizeObserver + direct DOM write), so dragging the sidebar handle resizes the card with it.

It is fully additive: nothing shipped is shadowed; closing the panel restores the normal session browser.

Architecture

Install into a profile

1. Make the package resolvable from the profile (Node walks $DSH_HOME/profiles/<name>/node_modules → $DSH_HOME/profiles/node_modules → …). A junction into this repo works:

   New-Item -ItemType Junction -Path "$env:DSH_HOME\profiles\node_modules\dsh-file-explorer" -Target D:\Codes\dsh-file-explorer
   

2. Add a row in the profile's cordis.patch.yml:

   - insert:
       - id: file-explorer
         name: dsh-file-explorer
   

3. Restart the profile (dsh web) and refresh the page. The browser bundle is picked up by the client-modules scan; subsequent edits to lib/client.js hot-reload through the HMR poll without a server restart.

Development notes

• Client slot targets: sidebar.footer.action (list, additive) and shell.overlay (list, additive); both are root-scoped, declared by the shipped ui-sidebar / ui-layout entries.
• The host route only accepts POST with content-type: application/json (cross-origin pages are forced into a CORS preflight the server never answers — the same fence the /api gateway relies on).