DeepSeek Harness Plugin

FNOSP/fnos-dsh#dsh-midscene-plugin

Category Tools & Capabilities Added 2026-10-17

Runs Midscene on the models already configured in DeepSeek Harness instead of separate third-party API keys: hosts an OpenAI-compatible bridge on 127.0.0.1 (default port 8787, automatically skipping occupied ports) that proxies chat completions, streaming and non-streaming, to the DSH host model layer, so DeepSeek official routing, CodeBuddy, Codex and custom OpenAI/Anthropic endpoints all become available to Midscene agents while credentials stay inside the provider plugins and the bridge never touches them. A `/v1/midscene-env` endpoint generates the four MIDSCENE_MODEL_* environment lines with the model family inferred, and seven built-in skills — browser, desktop, Android, iOS and HarmonyOS automation plus a Vitest E2E skill and a Midscene knowledge reference — appear in the session skill catalog without `npx skills add`. Install from npm with `dsh plugin --profile web add @tnnevol/dsh-midscene`.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:FNOSP/fnos-dsh#path:/plugins/dsh-midscene-plugin

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

Links

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.