dsh-orb
可安装的 Orb 捆绑包。插入 Computer Use 预设和悬浮球主机。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-orb@0.1.7Orb 以 dsh-orb 发布，当前版本为 0.1.7。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 中文
An unofficial personal plugin for DeepSeek Harness (dsh). One installable bundle that adds a floating-ball agent with Computer Use to the official dsh desktop app and dsh web — the official repository stays untouched, and the main window remains the official dsh Web UI.
Disclaimer — This is an unofficial project maintained by an individual developer. It is not affiliated with, endorsed by, or connected to DeepSeek AI in any way. DeepSeek, the DeepSeek logo, and the DeepSeek avatar artwork are the property of DeepSeek AI; they appear here only as the default ball avatar shipped by the upstream project.
A floating ball rests at the right edge of your screen. Tell it what you need: quick, visible actions are executed directly in the current app through Computer Use; long-running complex tasks are dispatched to a background coding session, and the result comes back to the ball when it finishes. The main window keeps the full dsh Web UI — session management, the plugin market, and model settings — so you can still write code, edit files, and run commands in it.
There is no telemetry.
On startup the plugin spawns its own helper (a pinned, verified Electron runtime in an isolated profile) and the ball appears at the right edge of the primary display, always on top.
$…$, $$…$$, \(…\), \[…\], the version the main window bundles, following the light/dark theme), copy buttons for user and assistant messages, and a per-turn token-usage pill.The Computer Use agent inside the floating ball decides how every message is handled; there is no separate task classifier at runtime:
flowchart TD
user["You speak to the floating ball"] --> orb["Computer Use Agent"]
orb -->|"Visible GUI actions"| gui["13 GUI tools<br>executed in the current window"]
orb -->|"Quick lookups: weather, news"| web["web_search / web_fetch<br>answered on the ball"]
orb -->|"Dig through files, produce documents or websites"| bg["code_agent background session<br>queued, returns immediately"]
bg -->|"Completion notice"| orb
web_search / web_fetch.code_agent to a background standard session. Dispatch returns immediately; the ball tells you the background is running and you can keep chatting. When the background session ends and the ball is idle, the completion summary returns to the ball automatically, and the Computer Use agent decides the next move — keep clicking, dispatch more background work, or wrap up.A background session is the same kind of session you create manually in the main window; it appears in the dsh_orb folder in the main-window sidebar, where you can open, continue, or stop it. Follow-up changes to the same deliverable go back to the same background session; unrelated new work opens another one. The conversation history, permissions, and per-track model settings are shared with the official dsh process — the ball reads and writes the same sessions as the main window.
Every conversation on the ball runs Computer Use: the first message automatically attaches a screenshot of the frontmost app's visible windows, and another screenshot follows every action, including your mouse cursor, so the model always sees the latest screen state.
click (single/double/right click, hold modifiers), input_text, scroll, hotkey, long_press, drag, wait, long_wait, screenshot (saved to the Desktop and copied to the clipboard), open_in_browser, open_in_finder, list_apps, open_app.dsh web) — authorize that process. The ball's onboarding layer walks you through Screen Recording and Accessibility.DeepSeek Harness (official, unmodified)
└─ Electron shell (main window, dsh://open, single instance)
└─ Host, spawned as a plain Node process (ELECTRON_RUN_AS_NODE=1)
└─ dsh-orb plugin
├─ host — sessions, permissions, models, web routes, helper lifecycle
├─ computer-use — 13 GUI tools + code_agent (Computer Use preset)
└─ client-settings — the "Floating Ball" section in main-window settings
Helper (its own downloaded Electron, isolated userData)
├─ ball window, observation border
└─ data requests → authenticated loopback URL of the official Host
dsh-orb bundle assembles the host, the Computer Use plugin, the helper, and the settings page into itself at build time.userData, separate from the official app.dsh web from the CLI. Built against dsh 0.1.7-rc.2; the declared compatibility range is >=0.1.7-rc.2 <0.3.0-0.^22.19.0 || >=24.0.0 and pnpm 11.7.0 (only for building from source).Releases are published to the npm registry and served from npmmirror. The install unit is the release tarball — not the repository itself: pasting the repo URL into a plugin page installs the monorepo root package, which fails with "this package declares no bundle".
By name — add dsh-orb in the desktop app's plugin page, or:
dsh plugin add dsh-orb
By version — dsh-orb@<version>. An explicit version skips the release-age gate, and pnpm records integrity from registry metadata. Do not paste a remote tarball URL such as https://registry.npmmirror.com/dsh-orb/-/dsh-orb-<version>.tgz: pnpm 11.7, which the official client bundles, rejects that URL because the lockfile entry has no integrity.
A just-published version can resolve to the previous one for up to 24 hours. The official client bundles pnpm 11, whose minimumReleaseAge default (1440 minutes) makes a named install settle for the newest version published more than 24 hours ago — a supply-chain guard, not a network problem. To get a fresh release immediately, install dsh-orb@<version>, or exempt the package in the profile's pnpm-workspace.yaml:
minimumReleaseAgeExclude:
- dsh-orb
With an older version installed there is no need to reinstall: the floating-ball card in the main window's settings page checks for and installs updates, and records the exemption itself.
Does the in-app update fail with operation-error? Releases through 0.1.4 handed pnpm 11.7 (the client bundles that version) an npmmirror tarball URL. That URL is stored without an integrity field, so pnpm rejects it before downloading (ERR_PNPM_MISSING_TARBALL_INTEGRITY) and the card only shows the generic operation-error. Install dsh-orb@<version> from the plugin page — not the tarball URL. After that, the update button installs by version and asks npmmirror first. The raw failure detail lives in the profile's .plugin-manager/logs/operation-*/pnpm.log.
pnpm install
pnpm build
pnpm --filter dsh-orb run pack # produces ./dsh-orb-<version>.tgz
runis not optional. A barepnpm packis pnpm's own command: it packs the workspace folder by itsfileslist, so none of the bundlednode_modules(koffi,zod, the platform prebuilds) end up in the tarball. The result installs, but the plugin cannot loadkoffiand Computer Use fails.run packexecutes the bundle'sscripts/pack.mjs, which assembles every part into the package.
Then either add the tarball in the desktop app's plugin page, or:
dsh plugin add ./dsh-orb-<version>.tgz
After the first installation the helper's Electron runtime is downloaded on first use of the ball, then cached.
pnpm typecheck # tsc over all packages
pnpm test # node:test suites + vitest suites (computer-use)
pnpm build # build every package and assemble the bundle
The design documents this plugin was built from live in docs/ — feasibility analysis, architecture, phased plan, and the running addendum of post-design revisions.
0.1.7-rc.2; newer dsh versions within the compatibility range may require re-verification.This repository is an unofficial derivative work built on top of deepseek-ai/deepseek-harness, dsh's open-source everything-is-a-plugin agent harness; sessions, plugins, tools, and the Web UI are all driven by it. This project modifies no upstream code — it installs like any third-party dsh plugin. To go deeper:
MIT. Upstream-derived code and assets are disclosed in THIRD-PARTY-NOTICES.md.