dsh-bridge

██████╗ ███████╗██╗  ██╗  ██████╗ ██████╗ ██╗██████╗  ██████╗ ███████╗
██╔══██╗██╔════╝██║  ██║  ██╔══██╗██╔══██╗██║██╔══██╗██╔════╝ ██╔════╝
██║  ██║███████╗███████║  ██████╔╝██████╔╝██║██║  ██║██║  ███╗█████╗
██║  ██║╚════██║██╔══██║  ██╔══██╗██╔══██╗██║██║  ██║██║   ██║██╔══╝
██████╔╝███████║██║  ██║  ██████╔╝██║  ██║██║██████╔╝╚██████╔╝███████╗
╚═════╝ ╚══════╝╚═╝  ╚═╝  ╚═════╝ ╚═╝  ╚═╝╚═╝╚═════╝  ╚═════╝ ╚══════╝

Familiar harness commands for DeepSeek Harness, with every plugin audited first.

Rendered from the specs rather than a running build. Stills: detection matrix (light) · trust card (light).

What

dsh-bridge is a DeepSeek Harness plugin for people arriving from Claude Code, Codex CLI, OpenCode, or Jcode. It ports the slash commands you already know onto DSH-native seams, adds a guided connectors flow, and refuses to recommend a community plugin until an adversarial review has graded it.

Why

• Language. The DSH plugin ecosystem skews non-English. The catalog and command surface here are English-first.
• Trust. Plugins are arbitrary code. Every recommendation ships a report card citing file-and-line evidence you can re-check.
• Muscle memory. /model, /resume, /memory, /mcp, /review behave the way your previous harness taught you.

Install

npx create-dsh-bridge

That is the whole thing. It checks Node and pnpm with a concrete fix for each failure, installs the DSH runtime if none is on your PATH, creates an isolated DSH_HOME so your real ~/.dsh is untouched, installs dsh-bridge into the web profile, wires the profile config, and prints the command to boot.

Re-running is safe: every step checks for its own result first and reports "already done" instead of repeating work, and it never overwrites a file it did not create.

See exactly what it will do before it does anything:

npx create-dsh-bridge --dry-run     # prints every command and file write, changes nothing

Useful flags: --ref <sha> pins both the installer and the plugin so a later push cannot change what runs, --profile <name> picks a different profile, --no-isolate uses your real ~/.dsh instead of a scratch home.

Prefer not to pipe from npm? The installer is a single readable file:

curl -fsSLO https://raw.githubusercontent.com/beartackler/dsh-bridge/main/scripts/install.mjs
less install.mjs && node install.mjs --dry-run
node install.mjs

What you still have to do yourself

DSH ships no model, and the installer connects none. When it finishes you have a harness that boots and a bridge that answers /bridge-help, and nothing that answers a prompt. Bring a provider endpoint and an API key, then run /bridge-setup in the UI. The full walkthrough, including a working custom OpenAI-compatible provider block, is in docs/getting-started.md.

The installer verifies the first two and stops with the command that fixes them. It cannot supply the third.

Manual install

If DSH is already installed, a model route is already connected, and you only want the plugin:

dsh plugin --profile web add github:beartackler/dsh-bridge
dsh --profile web        # serves http://127.0.0.1:3080

Both of those conditions matter. Without a connected route the harness boots and nothing answers; without .credentials.yaml at mode 600 it refuses to boot at all. docs/getting-started.md covers each step by hand.

Pin a commit so a later push cannot silently change what runs:

dsh plugin --profile web add "github:beartackler/dsh-bridge#<commit-sha>"

The repository ships its compiled dist/ output, so nothing builds on your machine at install time and dsh asks for no build-script permission.

Then use /bridge-help inside DSH.

Verified against @deepseek-ai/dsh 0.1.1-rc.2: a fresh install from a git checkout activates the bundle with no warnings and all 17 commands register (how this was verified).

Verified catalog

docs/catalog/INDEX.md lists every plugin that has completed a trust review, with the audited commit and a linked report card.

Grades: A verified-clean · B safe with documented behavior · C use with awareness · D risky · F do not install. A grade is an evidence-backed opinion over one pinned commit, not a safety guarantee.

Commands

All seventeen commands are implemented and verified end-to-end against @deepseek-ai/dsh 0.1.1-rc.2 (42 live invocations, see the verification report).

Naming caveat: shipped names will be either /bridge:<name> or /bridge-<name>, pending an open DSH parser question.

Docs

• Architecture — how the plugin sits on the Cordis kernel.
• Trust pipeline — grading bands, heuristics, provenance checks.
• Command specs · Plugin author guide · Glossary · FAQ
• Charter · Contributing · Security · Roadmap

Status

Under active development. Research and audit artifacts land in docs/ as they are produced.

Principles

1. Trust over speed. Every security claim cites evidence.
2. English-first, i18n-ready.
3. Minimal code. Shortest correct implementation, no speculative features.
4. You own your machine. No telemetry without opt-in.

Provenance

Cross-reviewed by design: adversarial reviews are performed by models that did not write the artifact under review. Quality gates are documented in CONTRIBUTING.md.

Not affiliated with DeepSeek. Built on their MIT-licensed groundwork with gratitude.