omdsh-plugins/omdsh-remdev

安装

That is the whole of the seam. [`omdsh-sidepanel`](https://github.com/omdsh-plugins/omdsh-sidepanel) and [`omdsh-codemode`](https://github.com/omdsh-plugins/omdsh-codemode) each gained one structural view of it and one branch; neither imports a value from this package, and neither knows what SSH is.

## A mounted project's skills

The harness discovers skills from the session's `cwd`: its own filesystem provider walks `<project>/.dsh/skills` and `<project>/.agents/skills` through the LOCAL filesystem service. A remote workspace's `cwd` is its mirror directory — an empty local stand-in — so the server's project skills are invisible to an agent running here. This plugin registers a provider (`remdev`) on the harness's `skills` service to close exactly that gap: when the `cwd` resolves to a mount, it reads the two skill directories back over SFTP into the same catalog — directory bundles and flat Markdown skills alike, parsed with the harness's own frontmatter grammar (name, description, `whenToUse`, invocation policy, metadata).

Four things are worth writing down:

- **It reads two fixed paths inside the mount.** The fence is the same one the file browser uses; a skill can never reach anything outside the mounted directory, and an unreadable skill file is skipped with a log line rather than failing the rest.
- **A skill's `resourceBase` is `opaque`, not `directory`.** The templates and scripts a skill references live on the server, where the local file tools cannot read them, so the model is told where they are and how to get there instead of a path its `read` tool would fail on. To use those resources, open the remote file panel or a remote terminal; a Code-mode agent already runs on the server and reads the same `.dsh/skills` locally there.
- **Remote changes are not watched.** The catalog re-reads when the registry's cache invalidates — a changed mount table (attached or detached folders, edited servers) does that — so a skill added on the server appears on the next refresh, and the same goes for a skill file edited mid-session.
- **An unreachable server simply contributes no skills.** The harness marks the observation incomplete and retries on a later boundary; user skills in the local `~/.dsh/skills` are unaffected.

## `.dsh-server`

The layout is `.vscode-server`'s, for the reason VS Code chose it — a remote install has to survive a server having its own Node, the wrong one, none, or several:

把 omdsh-plugins/omdsh-remdev 加入你的 DSH 配置（web profile）即可启用。