ssjob123/dsh-file-panel-left1

dsh-file-panel-left

DSH web plugin: a VSCode-like left file panel (file explorer / editor / preview), isolated per conversation session. Exposes a service for other plugins to register sidebar tabs and file viewers.

包名
dsh-file-panel-left
版本
1.0.1
许可证
MIT
最近更新
2026年8月21日

安装

$npx -p @deepseek-ai/dsh dsh plugin --profile web add github:ssjob123/dsh-file-panel-left

Usage

  • File tree: single-click a file to open it; use the tree-header or folder-row “+” to create files (Enter creates / Esc cancels); the search box filters by name; right-click a row to copy its path, rename, or delete
  • Editor: code and config files open in the CodeMirror editor; Ctrl/Cmd+S saves and the auto-save poller writes every second; Ctrl/Cmd+F searches; code/config files get folding, bracket matching, and column selection; JSON files show a format button (Ctrl/Cmd+Shift+F)
  • Preview: Markdown files toggle between Preview and Edit (Mermaid diagrams render in preview); HTML files render in a sandboxed iframe with a refresh control; images and PDFs preview directly; unsupported binary types show a notice
  • Context menu: copy relative path, copy absolute path, rename (duplicates are rejected), delete (confirmed, then moved to the Recycle Bin)
  • @-reference: select code in the editor and release the mouse, then click “Add to conversation” in the popup — the draft gets a blue @relative/path L12-L25 capsule; the tree's “@file” button references a whole file in one click

Configuration

The plugin has no settings page — behavior is built-in by design:

  • Expanding the panel = 65% of the viewport width (drag to fine-tune; remembered per session)
  • Auto-save: polls every 1 second, writes only when there are unsaved changes; cannot be disabled
  • Chat file-open interception: always on (tool rows, produced files, mentions all open in the sidebar); no toggle
  • Delete: confirmed, then moved to the system Recycle Bin / Trash (Windows 10/11 and macOS)
  • HTML preview: sandboxed by default (no access to GUI data or local files)
  • Preferences (e.g. title-bar compatibility) persist through the settings service; deployments without one fall back to a local file