dsh-plugin-bridge

English | 中文

Halfway through a task and need another tool preset? Switching the produced session in place would leave tool history that belongs to the old assembly. Bridge previews a bounded five-part handoff, opens a clean target, and leaves the original session untouched.

Quick start · Why Bridge · Evidence · Decisions · Compatibility

Quick start

Bridge 0.5.0 adds a conversation-menu action, a configurable shortcut and natural-language preparation, while keeping preview, editing and human confirmation. The candidate passed isolated official 0.2.1-rc.2 Web and native macOS Desktop handoffs and a keyless 0.2.0-rc.2 backward check. The acceptance record separates runtime tests, their limits and pending publication checks. The bounded 0.2.1 admission policy introduced in 0.4.7 remains unchanged; see Support policy before treating an admitted future version as tested.

Check the Host's actual pnpm executable when installing or removing packages. pnpm 11.22.0 has a known late-worker shutdown bug that can keep a package operation alive after printing Done; natural DSH reproductions isolated the upstream fixes. Use 11.26.0 or later, which includes the upstream fixes, and avoid overlapping package operations. If an operation is pending, wait for it to settle or stop the Host normally before using the offline CLI. Bridge does not bundle pnpm or upgrade your tools automatically.

npm / CLI

Install from npm:

dsh plugin --profile web add dsh-plugin-bridge

On DSH 0.1.5-rc.2, restart dsh web after adding or removing the plugin. On DSH 0.1.6-alpha.2, a first install from the WebUI Plugins page applies live; CLI install and upgrades may still need one restart. DSH 0.1.7-alpha.1 was tested with CLI installation, live disable/enable, and removal followed by a restart; restart-free installation or upgrades were not tested.

On DSH 0.2.1-alpha.3 / 0.2.1-alpha.4 Web with HMR, the running pluginManager service's installBundle() API, including Remote API callers and the agent's plugin_manager tool, returns already-installed for a package already in the profile, even when another version is requested. API replacement uses removeBundle(name) followed by installBundle(spec); honor any restart request. See the upstream upgrade guide.

For CLI replacement, stop the Host using the selected profile, run dsh plugin --profile web remove dsh-plugin-bridge, then dsh plugin --profile web add <desired-package-spec>, and start the Host again. The CLI runs separate profile package operations; the running-API refusal above does not apply to that path.

…