dsh-remote-file-system

DSH natively reads and writes only the local file system. The moment a task touches a remote host configuration, log, or codebase, the model is forced back into hand-crafted ssh-plus-sed-and-awk one-liners, where a single typo can silently fail or overwrite the wrong file. dsh-remote-file-system collapses that fragile chain into three first-class tools the model can invoke directly: read_remote, write_remote, and edit_remote. SSH transport becomes an invisible layer instead of something the prompt must manage.

Each tool has a tight contract. read_remote returns line-numbered UTF-8 pages with the same offset, limit, and totalLines shape as the native read, so downstream parsing stays uniform. write_remote is create-only: if the target path already exists it is rejected outright, eliminating any accidental overwrite branch. edit_remote performs a literal string replacement that must match exactly once by default; multiple hits are rejected, and a non-hit is an explicit error, while replace_all is available for batch substitutions. The address is written as ssh-alias:remote-absolute-path, the alias being pulled from the local SSH config, and bare relative paths are refused. Rendering stays compatible with diff display, and writes pass through the same rule-guard checks used locally, keeping the review pipeline consistent.

If your daily DSH sessions involve letting the model maintain configs, triage logs, and batch-edit code on remote servers without re-prompting it to spell out SSH commands every time, these three tools give it a safe, standard surface to work on.