dsh-dir-tree

简体中文 | English

> A DeepSeek Harness (DSH) floating workspace directory-tree plugin: drag-and-drop file/folder paths into the chat box, lazy loading, search, file-type icons, and auto-follow when switching workspace/session.

> 📚 Full three-form showcase repo (install & internals comparison of dynamic / persistent / standard bundle): dsh-plugin-dir-tree

Features

• 📁 Floating directory tree of the current session's workspace, minimizable at the bottom-right corner
• 🌲 Lazy loading: click ▶ to expand subdirectories; large directories stay responsive
• 🖱️ Drag files/folders into the chat box; the full path is filled in automatically
• 📋 Double-click to copy a path; single-click to select
• 🔍 Search filter for file names
• 🎨 File-type icons + directory 📁/📂 blue highlight + indented tree lines
• 🔄 Switches workspace/session and the tree follows automatically
• 🪟 Draggable floating window position

Screenshots

Main UI (floating window + directory tree)


The floating window "📁 Current Workspace" sits in the bottom-right corner: the full path on top, the tree below — directories in blue with a 📁 icon and a ▶ expand arrow, files with type icons.

Drag a path into the chat box (animation)


Drag any file/folder node into the chat input box; the full path is filled in automatically.

Lazy-load expansion (animation)


Click the ▶ of a folder to expand its children; only the current level is loaded, so large directories stay responsive.

Minimize / Restore


Click − or × to collapse the window; a blue "📁 Directory Tree" button appears in the bottom-right corner. Click it to restore.

Installation

This is a standard bundle for DSH — install with dsh plugin add, with no source checkout, no editing of built-in packages, and no Creator mode.

0. Install/run DSH (pick one)

Option A: Global install (recommended for daily use)

npm install -g @deepseek-ai/dsh

Option B: Run temporarily with npx (no install, occasional trials)

npx @deepseek-ai/dsh web

> Both share the same $DSH_HOME (default ~/.dsh) and profile directory — plugins/sessions/config are fully interchangeable, so this doesn't affect the plugin install below.

1. Install the plugin

Option 1: Install from npm (recommended — no authorization needed)

The plugin is published on npm, one command:

dsh plugin --profile web add dsh-dir-tree

Option 2: Install from git (no npm publish involved)

dsh plugin --profile web add github:bentong-chain/dsh-dir-tree

On first install you'll be prompted to add a build authorization to pnpm-workspace.yaml in your profile:

allowBuilds:
  dsh-dir-tree: true

Copy it and re-run dsh plugin --profile web add github:bentong-chain/dsh-dir-tree.

2. Start DSH (web UI)

dsh web is a hard-coded alias of dsh --profile web — fully equivalent; all three spellings start the same web profile (~/.dsh/profiles/web):

# Option A: after global install (recommended)
dsh --profile web        # or the equivalent alias: dsh web

# Option B: temporary npx run (equivalent to above)
npx @deepseek-ai/dsh web

> No matter how you start it, the plugin loads normally — startup method doesn't matter.

Usage

1. After starting DSH (dsh --profile web / dsh web / npx @deepseek-ai/dsh web), the "📁 Current Workspace" floating window appears in the bottom-right corner 2. Click a folder's ▶ to expand its subdirectories 3. Drag files/folders into the chat input box to fill in the full path 4. Double-click to copy a path; use the search box to filter; click −/× to minimize; restore via the bottom-right button

Structure

dsh-dir-tree/
├── package.json       # dsh.bundle + dsh.client + prepare build script
├── cordis.patch.yml   # inserts the plugin row
├── index.js           # Host half (connection.rpc.handle + node:fs directory listing)
├── client.js          # Client half source (floating UI + connection.rpc.call)
├── client.bundle.js   # build output (generated by prepare, not committed)
├── build.mjs          # prepare script: esbuild bundling of client.js
└── docs/              # README screenshots (main UI/drag/lazy-load/minimize)

Technical Notes

• RPC: uses ctx.connection.rpc (a Client→Host channel available to third parties); no api-remotes, no Typert code generation.
• Workspace tracking: the Client half reads the current session's cwd from ctx.sessions and passes it to the Host; it refreshes reactively when the workspace/session switches.
• Directory detection: the Host uses node:fs's readdir({ withFileTypes: true }) to get Dirent.isDirectory() directly — no per-entry stat, so large directories stay responsive.
• ⚠️ exports must include ./package.json: client-modules locates packages with require.resolve('<pkg>/package.json'); if an exports field is defined, any subpath not listed fails to resolve and the client half is silently skipped (no error, never reaches window.__DSH_BOOT__). Always include "./package.json": "./package.json".
• ⚠️ The Client half must import React from 'react': in a persistent client bundle, React is not a global — it must be fetched from the browser module table via require('react') (react is one of the platform modules); referencing a global React throws ReferenceError at apply time.

License

MIT