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

Install from npm:

dsh plugin --profile web add dsh-plugin-bridge
# restart dsh web once

Pinned GitHub fallback:

dsh plugin --profile web add github:Totoro-qaq/dsh-plugin-bridge#v0.2.10

Then type in the official WebUI:

/bridge                       list target presets
/bridge --doctor              check the host contract after a DSH upgrade
/bridge code                  preview the handoff; change nothing
/bridge code --go             migrate, restate, then wait
/bridge code --go --continue  restate and start work in the same target request

The preview is editable. Correct a number or path in the printed summary file, then run:

/bridge code --go --file <path>

Uninstall with dsh plugin --profile web remove dsh-plugin-bridge, then restart dsh web.

Why Bridge

Promise	What it means
Preview before execution	/bridge <preset> creates no target and changes no source session. Review or edit the five-section handoff first.
Move state, not tool traces	Decisions, paths, current state, and next steps move to a clean preset. Incompatible calls from the old tool assembly do not.
Fail closed	The target goal is paused before kickoff. If that cannot be guaranteed, Bridge clears/cancels the target and sends no model request.

Installing Bridge adds zero prompt tokens to ordinary sessions. It is a host slash command, not a model tool or skill.

Evidence at a glance

The release gate is intentionally small and reproducible; these are regression results, not population guarantees.

Gate	Result
Five-part summary facts	30/30
Target restatement / first useful work facts	60/60 · 60/60
Critical facts / obsolete-value resurrection	90/90 · 0
Existing image evidence / unresolved raw image	5/5 · 5/5
Confirm / --continue target request shape	2 · 1 to first useful work
Confirm extra, paired nominal median	+8.1% vs --continue
Summary worker share of clean acceptance components	20.74% nominal

The token percentage varies widely with preset, response length, and cache state. The worker share is composition, not causal overhead versus no Bridge; the stable product claim is one additional confirmation request. Read the design and evidence boundaries, full release report, and vision report.

How it works

fold history -> five-part handoff -> preview/edit -> clean target session
             -> pause stored goal -> inject -> restate -> wait or continue
image history -> verbatim assistant evidence; unresolved originals use the attachment gateway

The five sections are Goal, Current state, Key decisions and conventions, Key files, and Next step. The original session is never rewritten; archive the target and return to the source if the handoff is unsatisfactory.

Migration decisions

…