DSH is a Cordis-based agent harness (deepseek-harness). OCP runs unmodified OpenCode aisdk-type plugins as LLM adapters via @opencode-compat/dsh-bridge.
Authoritative contract: packages/dsh-bridge/README.md. This page is the family install/verify guide. The discovery plan under tasks/plans/ is historical.
DSH is not an OpenCode clone and has no @opencode-ai/plugin-shaped package, so the facade/ocp setup mechanism does not apply.
Instead, @opencode-compat/dsh-bridge is a Cordis plugin (name/inject/Config/apply) that dynamically loads unmodified OpenCode plugins and registers each as a ctx.llm.registerAdapter() LlmAdapter:
| Discovered | From the plugin's own… |
|---|---|
| provider id | auth.provider (else package name, de-collided against deepseek-official etc.) |
| model catalog | config hook — config.provider[id].models, models.dev entry shape, variant effort → DSH ACP reasoningEffort |
| API key | CredentialRef env name (CURSOR_API_KEY, DEVIN_API_KEY — native, not DSH_-prefixed) via ctx.credentials.resolve, then the plugin auth.loader |
| streaming | createXxx() AI-SDK V3 factory (doStream) → StreamChunk |
| session affinity | GenerateOptions.sessionId (DSH-native) → V3 headers["x-opencode-session-id"] |
Host variance is data (DshHostProfile single dsh profile) — same rule as HostProfile/PiHostProfile.
The structural skills bridge uses the current request's published catalog and passes its workspace and agent to skills.list(). Skills hidden from model invocation, unadvertised entries, and virtual skills without file locations are omitted. A replacement empty catalog clears earlier entries.
dsh plugin --profile web add @opencode-compat/dsh-bridge
# then set config.providers[].package (npm name or absolute dist/index.js)
# restart dsh web@opencode-compat/dsh-bridge and @opencode-compat/opencode-loader ship in the same train. The provider package is loaded by the bridge from config.providers[].package; it does not need to be listed as a DSH bundle.
No dsh-bridge.json file search. Configuration is the Cordis patch config.providers[] (native DSH cordis.patch.yml):
# $DSH_HOME/profiles/web/cordis.patch.yml (written by `dsh plugin add`)
- insert:
- id: ocp-dsh-bridge
name: '@opencode-compat/dsh-bridge'
config:
providers:
- package: cursor-opencode-provider
providerName: cursor # optional
apiKeyEnv: CURSOR_API_KEY # CredentialRef env name, not a secret
createOptions: { apiKey: "$apiKey" }
- package: devin-opencode-provider
apiKeyEnv: DEVIN_API_KEYOnly package is required. The same OpenCodePluginSpec shape as pi-bridge is accepted (providerName, apiKey, createOptions, disableOAuth, preferAuthMethod, splitDimensions, directory) but stored in yml, not a JSON file. apiKeyEnv names the CredentialRef; apiKey is its alias, but only apiKeyEnv drives the Settings → Models key badge.
Settings → Models lists each registered route as a configured row addressed into the bridge entry's volatile providers Config (DSH keeps live settings in the plugin's own Config). Editing providers in the patch re-registers the bridge live. See the settings contract.
Variant effort dimensions map to the host ACP effort picker via LlmResolvedModelInfo.reasoning.efforts.
The bridge also preserves the provider's context and output limits. Its bundle
selects an OCP token-meter provider through the native token-meter entry;
no extra user configuration is required. That meter delegates to stock DSH
and separates explicit provider context snapshots from billed token buckets.
See the accounting contract.
Local/npm switch is via scripts/ocp-dev.sh (DSH family, local checkout + npm mode — not ocp setup):
./scripts/ocp-dev.sh run dsh
./scripts/ocp-dev.sh run dsh --mode npmlocal runs pnpm install and the harness documented build (build:native-system, host/client lib, build:web; tsdown only for directories with package.json), builds local opencode-loader + dsh-bridge and the provider, stages dsh-bridge with a file: pin to the local loader (profile pnpm cannot resolve Bun workspace:* or an unpublished train pin), adds that stage via dsh plugin add, syncs those packages' dist, manifests, and bundle patch into the profile node_modules copy (pnpm file: does not pick up newly emitted files), and points the patch entry at the provider's absolute dist/index.js. npm switches back to bare npm names. Mirrors docs/hosts/pi-family.md:87 for pi/omp.
Train pin rule: packages/dsh-bridge/package.json must keep @opencode-compat/opencode-loader as an exact train pin, never workspace:*. Profile pnpm reads the source manifest on dsh plugin add file:… and fails with ERR_PNPM_WORKSPACE_PKG_NOT_FOUND otherwise (0.4.1 regression). bun scripts/bump-version.ts rewrites the pin and refuses workspace protocol on dsh-bridge / pi-bridge — see docs/guides/npm-publish.md.
- From a checkout,
node apps/cli/lib/bin.js webstarts (after the harness lib build). Do not usepnpm dsh web— that tsx source launcher dual-loadsdsh-toolsand every tool dies onprepare. Model picker showscursor/*(orcursor-opencode/*if de-collided) and, when the Devin checkout is wired,devin-opencode/*(devinis reserved on DSH). - One full turn: user → model stream →
StreamChunktool-call→ DSH executes → follow-up turn. - New provider = yml row only.
Programmatic smoke (no yml):
import { registerDshPlugin } from "@opencode-compat/dsh-bridge/src/register.js"
await registerDshPlugin(ctx, { package: "cursor-opencode-provider" })dsh-bridge remaps only the host tools that have an OpenCode-equivalent
vocabulary (same rule as pi-bridge providerName):
| Host | Advertised | Call remap |
|---|---|---|
todo_write |
todowrite |
strip id/priority/merge; omit cancelled |
ask_user_question |
question |
synthesize missing id; multiple ↔ multi_select; JSON {answers} → OpenCode "<prompt>"="<answer>" prose |
DSH's skill catalog (a user-role <system-reminder>) reaches every bridged
provider in the system prompt, as OpenCode and Pi place <available_skills>;
only the latest catalog is kept. A request that offers file tools also states
the home directory, because DSH file tools do not expand ~.
Before a bridged provider's read, read_image, edit, glob, grep, or
bash call runs, OCP checks its path argument (file_path, path, or
workdir) on DSH's public tools/pre-execute gate. A path that does not exist
is denied with the call to make instead: the absolute form of an unexpanded
~/…, the real home directory in place of a guessed one, or a glob lookup
from the nearest existing directory. write targets, nested dispatches, other
providers, and sessions whose workspace is not on the local disk are not
checked.
The canonical question tool is the visible, host-native way to collect a
choice, confirmation, or missing detail during a turn. A request that needs a
new user turn stays a standalone final reply, which DSH displays outside its
collapsed activity.
Cursor's optional OCP integration supplies plan_enter through the public
DSH /plan command, which reaches the calling agent's plan service even when
the service is isolated inside an agent preset. The host commits that selection at
its next step boundary, inside the same turn; the plan_enter result tells the
model to keep planning and submit before ending the turn. Cursor sees native exit_plan_mode as
cursor_plan_stage: the complete markdown content becomes DSH's {plan},
starting with #. DSH executes its original tool, displays the native review,
and owns approval, feedback, cancellation, and exit. The transcript retains
the submitted plan; no extra filesystem plan artifact is required.
Each session request runs the plugin's OpenCode chat.params hook with DSH's
plan mode as the OpenCode agent (plan or build), so a provider follows plan
mode however DSH entered it.
When Cursor ends in titled markdown plan prose without a tool call, OCP
submits that plan through the same native review while the calling agent's
logged plan state is active. The host transcript records a
host_plan_stage_ call id for this fallback.
Other providers retain the native name/schema. The catalog stays stable
across mode changes. OCP rewrites the tool reference in system guidance but
does not append mode events or inject execution follow-ups. /plan remains
available to the user. See the upstream
plan-mode README.
For Cursor-generated images, the bridge advertises cursor_image_save only to
Cursor. The tool accepts a single-use staged image ID and commits the provider's
bytes at the requested path. DSH's current sandbox policy decides whether an
approval prompt is needed; a save outside a workspace-write sandbox asks for
approval before writing. Other providers do not see this tool.
If DSH wakes Cursor again solely for a late subagent notice after a text-only reply, the bridge repeats that reply in the new final step without another model call. DSH keeps it visible outside collapsed activity. The display copy is excluded from later model prompts. This applies to any reply text, including requests for user input.
When Cursor spills a large discovered-tool catalog to its agent-tools/
metadata directory under the host cache, OCP supplies DSH's normal file-write
escalation fields. The native write asks for approval because this cache is
outside the workspace. OCP does not widen other file writes.
DSH sends AGENTS.md and scoped instruction files as user-role
agent-instructions messages. For Cursor, OCP moves them into the system
prompt, which the Cursor provider delivers as an always-apply rule; as separate
user messages they would be dropped on resumed turns or start a new turn after
tool results. Other providers receive DSH's messages unchanged.
On load, dsh-bridge installs Symbol.for("opencode.host.path-bridge"):
globalDataDir—$DSH_HOMEor~/.dshglobalCacheDir—$DSH_HOME/cache/opencode-providers(default~/.dsh/cache/opencode-providers), separate from a native OpenCode cacheprojectConfigDirs—<workspace>/.dshand<workspace>/.opencode