sjw1231
e2f1208bcf
Regenerate config/tool/module/event catalogs, Cordis API and client slot catalogs; re-record reviewed bilingual hashes instead of merging generated bytes. Accept deleted filesystem invariant companions. Master has no replacement event-invariant registration; keep delete-intent in typed events, policy guards, and behavior tests. Adopt master workspace-changes intent waterfalls and tool-execution recorder association, add a prepended delete-intent listener that delegates before capture, remove argument parsing and the fs-patch dependency, and retain the real-tool Review matrix. Keep master filesystem mutation-result metadata and tool switches alongside opt-in apply_patch. Await current-directory resolution in plan and no-follow preflight; store patch diffs as processPath. Adapt native/PTC fixtures to the supported modes. Preserve client patch diffs and stopped states with master partial arguments and absolute navigation. Use master's rewritten ProviderEditor, including its remaining repeated model validation. Regenerate the lockfile with pnpm install and align the new fs-patch package version. Clean retired package build outputs. Update exact rescope exceptions for verified preset and event identifiers from master; old package names remain rejected.
description, kind
| description | kind |
|---|---|
| Remote filesystem semantics for consumers sharing files with SSH subprocesses. | package-reference |
@deepseek-ai/dsh-fs-ssh
English | 中文
Summary
dsh-fs-ssh provides ctx.fs in the SSH helper’s filesystem. File tools read and mutate the same files that remote Bash, terminals, language servers and Node programs see. Remote canonicalization, version guards and atomic mutations use the local filesystem implementations installed beside the helper.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
Mount this provider with dsh-ssh and sandboxPolicy; use its paired SSH subprocess and sandbox providers for execution. This provider has no configuration fields: connection identity and the default workspace belong to dsh-ssh, while file-effect mode belongs to sandboxPolicy.
resolve() canonicalizes paths on the remote host. processPath() and fileUrl() name files in that same remote namespace; they do not grant host-side access. File URLs encode literal percent signs, backslashes and newlines without changing the filename. processPathFromHostPath() returns undefined, so consumers requiring an installed executable or bootstrap must supply a remote artifact explicitly.
Reads preserve shared filesystem error codes. All five mutations send per-call policy to the helper. patchText, deleteFile, and moveFile use fs.patch, fs.delete, and fs.move; their guards and results follow the local provider, including a published destination with failed source removal. Responses are strictly validated. Cancellation or transport loss can leave the remote outcome unknown; no request is replayed and no committed effect is rolled back.
Understand the implementation
Implementation internals — click to expand
The helper reuses fs-local and fs-sandbox, preserving symlink identity, stale-version rejection, diff bases and publication semantics. UTF-8 streaming uses bounded pull requests and closes its remote iterator when the consumer stops early.
Further Exploration
- Filesystem subsystem — shared operations and error meanings.
- SSH connection — deployment and disconnection behavior.
Model Experience
Indirectly, through existing filesystem consumers, which present remote paths and file contents while owning every tool and prompt.
KV Cache effect
This provider contributes no request-prefix content. Its consumers own model-visible tools and results.
Known Limitations and Deferred Work
- Whole-text reads and individual byte windows are limited to 8 MiB by the helper. Use text streaming or multiple byte windows for larger reads; other JSON transfers also obey the connection’s frame cap.
- Filesystem watching is unsupported: the provider keeps no
watch()override, so the baseFS_IO_ERRORrejection applies without polling or opening a local watcher for a remote path. Ordinary reads and consumer-owned manual refresh remain available. - Remote file URLs are execution coordinates, not host filesystem handles or Web download links.
Dev Note
Working context for maintainers — click to expand
None.