a903067276-rgb/dsh-file-mentions
Clickable file paths in DSH replies: Codex-style inline open, 📂 reveal in file manager, mentioned-files chip list. DSH web plugin (zero-dependency).
Listed
8
Ui
Bundle verified
Preview
What it does
Clickable file paths in DSH replies: Codex-style inline open, reveal in file manager, and a mentioned-files chip list at the turn tail.
Best for
- DSH Web users who want backtick-wrapped paths in agent replies to open files or reveal them in the system file manager.
- Workflows that benefit from an automatically collected mentioned-files list for previewing files at the end of a turn.
Not ideal for
- Responses that use bare prose paths rather than backtick-wrapped paths, because bare paths are intentionally not made clickable.
- Windows or Linux deployments requiring verified platform behavior, or workflows needing unrestricted access outside the session directory; those platforms are untested, and external roots must be explicitly whitelisted.
README
dsh-file-mentions 📎
| English | 简体中文 |
Clickable file paths in DSH replies — a DeepSeek Harness (DSH) web plugin with a Codex-style experience.
Unofficial project: independently developed and maintained by a community member, not an official DeepSeek product.
Screenshot

Inline paths wrapped in backticks (`~/...`, absolute, relative, or Chinese paths) become
click-to-open; each clickable path carries a small folder-icon button that reveals the file in your
file manager; a “📎 mentioned files” chip list at the turn tail covers the rest. URLs are
already auto-linked by the official renderer, so this plugin leaves them alone.

The external-drive whitelist (Settings → Plugins → file-mentions): paths outside the session
working directory (external drives, ~/Desktop, etc.) become clickable once added — one path
per line. System-disk marker directories (/System, /etc) are rejected automatically.
Features
| Where | What | Effect |
|---|---|---|
| Inline path text | click | Open with default app / open directory |
| folder icon after inline path | click | Reveal in file manager |
| “📎 mentioned files” chip | click name | Preview content inside DSH |
| folder icon in the chip list | click | Reveal in file manager |
| Inline URL | click | Browser opens it (official autolink) |
Supports ~/ expansion, relative paths (resolved against the session cwd), and absolute
paths in macOS / Linux / Windows forms. Non-existent paths silently do nothing.
Install
This repository is an official bundle plugin (dsh.bundle + dsh.client in the root
package.json), installed through the official profile manager:
dsh plugin --profile web add "github:a903067276-rgb/dsh-file-mentions#main"
Then restart dsh web (bundle layers are composed at startup; HMR does not apply).
Requires pnpm on PATH (dsh plugin forwards to pnpm).
Manual mount fallback: see docs/install.md.
Usage
Have the agent wrap paths in backticks (e.g. `~/docs/plan.md`) to make them clickable
inline. The tail chip list appears automatically — no configuration.
Paths outside the session directory (external drives, etc.)
For safety, absolute/~/ paths are only probed inside the current session’s working
directory. To make paths on an external drive (e.g. /Volumes/USB) or any other directory
outside the session working dir clickable, add that directory to the external-drive
whitelist in Settings → Plugins → file-mentions (one path per line). Saving takes effect
immediately — no restart required.
System-disk protection: whitelist roots containing system marker directories (/System,
/etc, or \Windows on Windows) are rejected automatically, so a full system disk mounted
externally can never be whitelisted by mistake.
Platform support
| Platform | Status |
|---|---|
| macOS | ✅ Fully tested (incl. Chinese paths) |
| Linux | ⚠️ Not tested — expected to work (command branching and path parsing implemented) |
| Windows | ⚠️ Not tested — expected to work (command branching and path parsing implemented) |
Requirements
- DSH web (run with
npx @deepseek-ai/dsh web) - Pure Node stdlib implementation — peer dependencies (
@deepseek-ai/dsh-settings,@deepseek-ai/schemastery) are provided by the host - Opening files uses the system default app / file manager (per-platform command branching)
How it works
-
Host (
lib/index.js): three routes —/api/file-mentions/check(existence check),/api/file-mentions/open(system open,mode: open/reveal, per-platform command) and/api/file-mentions/config(whitelist read/write for the settings page, same-origin guarded). Probe surface: absolute/~/paths are checked only inside the session cwd or user-declared whitelist roots (stored via the official settings service — immediate effect, no restart); whitelist roots are protected against system disks and symlink escapes. Pure Node stdlib;execFileavoids shell injection. -
Client (
lib/client.js): a conversationEvents collector extracts paths from each reply → publishes them to turn data → the tail list filters non-existent paths before rendering; inline clicks use a document-level click delegation (the official render entry is occupied by the official “deliverables” plugin, so DOM delegation is the only viable path); inline folder-icon buttons are inserted by a MutationObserver and restored automatically after React re-renders; a settings card (sidebar section + plugin page) edits the whitelist.
See docs/architecture.md.
Notes
- Use either the official bundle install or the manual mount — never both.
- Manual mounting needs a single entry in
~/.dsh/cordis.patch.yml; a double entry applies the plugin twice and crashes on duplicate route registration.
Compatibility notes
- Inline clicks rely on backtick-wrapped paths (the agent-output convention, same as Codex); bare paths in prose are intentionally not clickable.
- The official “produced files” list and this plugin coexist: official wins when it has output, otherwise this plugin shows.
- Windows / Linux validation via issue or PR is welcome.
License
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:a903067276-rgb/dsh-file-mentions in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.