dsh-at-fileA77
@omdsh-devType @ in the DSH composer to search the current workspace and insert a file or directory path. The plugin passes the path only — never the contents — leaving it to the agent to decide whether to open it.
dsh plugin --profile web add github:omdsh-dev/dsh-at-file
The author hasn't published to npm, so this command installs from git source. pnpm ≥ 10 refuses to run a git dependency's prepare script until you grant it, so your first install needs an allowBuilds entry in that profile's pnpm-workspace.yaml — which means letting this package's code run on your machine. Pin a #commit while you're at it.
The name after --profile is a profile name you choose yourself — swap in whichever one you use.
Typing @ opens a picker, and the matched file or directory path drops straight into the draft; the selected path stays visible in the reference bar and can be opened or removed. The key design decision landed in 0.3.0: before the agent starts a step, the plugin confirms the path really exists inside the active workspace, then appends only a short reference message (a workspace-reference carrying the workspace-relative path and its kind). It does not open the referenced file or list the contents of a referenced directory — whether to look, and with which tool, is the agent's call based on the task. As a result file format and size are irrelevant to this path: a PDF follows exactly the same path-reference flow as any other workspace file. Only earlier releases read content at submission time and enforced size limits.
- ▸Passes the path, not the contents: since 0.3.0 it appends a workspace-reference message and lets the agent decide whether to read it
- ▸Consequently format and size do not matter — a PDF follows the same flow as any other file
- ▸Ranking favours exact names, prefixes and compact matches; a query with / matches path segments, ArrowRight enters a directory, and the default index skips VCS, IDE metadata, dependency trees, caches and build output
Codex 风格 @ 文件引用,行为边界写得清楚(只传路径不读内容),工程干净
Drop it into your README — it links back to this page.
