AI Agent Hub
Back to plugins
🖥️

dsh-file-mention

Client Updated 2026.08.15

Run the following command in DeepSeek Harness:

dsh plugin install Seryta/dsh-file-mention

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install Seryta/dsh-file-mention in DeepSeek Harness to install the plugin from https://github.com/Seryta/dsh-file-mention ; after installation, restart dsh web and refresh the page.

About this plugin

When you are steering an Agent through code changes in the DSH Web GUI, the most common request is "edit this file." Typing the full path by hand is slow and error-prone, while content-injection plugins dump large chunks of source into the context window, burning tokens and adding noise.

dsh-file-mention takes a lean approach: type @ in the composer and a shallow workspace file menu appears instantly; keep typing a fragment to fuzzy-filter, then select to insert a single @relative/path reference. No file content enters the context— the Agent picks up the path and uses its own local file tools to read, modify, or test. Ranking combines subsequence matching, basename weighting, and shallow-first preference. A background warm-up on session open plus a 30-second memory cache mean the menu pops up with near-zero latency. Once the cache is established, any file add or delete is detected immediately via mtime comparison, so new files show up within seconds. The plugin is pure handwritten JS with zero build steps and zero third-party dependencies.

It suits developers who regularly drive an Agent for code edits and file operations through the DSH Web GUI and want to keep the context window reserved for meaningful conversation rather than bulk source code.

Use Cases

  • Reference a code file mid-conversation so the Agent can locate and modify, test, or debug it
  • Quickly pinpoint a target path when the Agent needs to create, delete, edit, or inspect workspace files
  • Avoid dumping full source into context during large-file operations to save tokens

Best For

  • Engineers who steer an Agent through code development via the DSH Web GUI daily
  • Developers who frequently ask the Agent to read, create, rename, or move project files
  • Teams that value context-window efficiency and want to reserve tokens for conversation