dsh-augmentor
Augmentor for DeepSeek Harness：DSH 插件 + Chrome 扩展，可从任意 DSH 会话控制用户的真实浏览器——实时页面快照、点击、输入、标签页操作，并将聊天会话保存到工作区。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-augmentor@0.2.13Augmentor 以 dsh-augmentor 发布，当前版本为 0.2.13。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
The DSH-side half of Augmentor: it mounts into a DeepSeek Harness web profile and gives any DSH session the tools to drive the user's real Chromium-based browser (page snapshot, click, type, tabs) through the Augmentor Chrome extension, plus the chat-lifecycle surface (dedicated chat dir, save-to-workspace sessions) the extension panel uses.
The package is a cordis
bundle: dsh plugin add installs it into a profile and its dsh.bundle.patch
layer mounts the plugin automatically.
Version 0.2.11 pins the security-fixed ws 8.21.3. Use the matching Browser
and companion from the complete release.
Updating this npm plugin alone does not update an older companion or extension.
web)Published npm package (check its version and shipped license):
dsh plugin --profile web add dsh-augmentor@0.2.11
From git (no npm needed):
git clone https://github.com/ManoloRemiddi/augmentor-agent.git
dsh plugin --profile web add /path/to/augmentor-agent/apps/browser/plugin
dsh plugin is a thin pnpm forwarder: it installs the package into the
profile's node_modules, sees the dsh.bundle.patch declaration, and adds the
package to dsh.profile.bundles — the next profile boot composes the plugin's
patch layer and mounts it.
Note on build scripts: the
preparescript rebuildsdist/index.js(the bundled entry) with esbuild. A pre-builtdist/ships in the repo, so if pnpm's build-script policy blocksprepare(pnpm ≥ 10 default), the install still works — or allow the build in the profile'spnpm-workspace.yamlunderallowBuildsand re-run.
Declared in the profile's cordis.patch.yml (the plugin's patch layer supplies
the entry; config rows can be added there):
| key | default | meaning |
|---|---|---|
apiPath | /api/augmentor | HTTP handshake route under the DSH app |
wsPath | /api/augmentor/ws | WS upgrade route for the pipe channel |
commandTimeoutMs | 30000 | per-action browser round-trip timeout |
wsToken | (empty) | action-channel token; empty = per-machine secret file ~/.dsh/augmentor-ws-token (created 0600 on first boot) |
chatDir | ~/Augmentor | dedicated directory Augmentor chats live in (~ expands) |
agentPreset | augmentor | agent preset for extension sessions (carries the browser-control persona) |
workspaceTitle | Augmentor | workspace the Save button attaches sessions to |
The pipe (the extension's native-messaging host) connects to wsPath, gated by
the token (header x-augmentor-token, legacy ?token= fallback on the plugin
side). Frames are JSON objects; the canonical vocabulary lives in
../wire.mjs (shared by pipe, plugin, and the extension
service worker):
welcome {name, protocol, version} — plugin → pipe, once on connectrequest {id, method, params} / reply {id, result | error} — both
directions; browser/execute goes to the active pipe only, and its reply
must come from that same socketbrowser_tabs_list, browser_navigate, browser_snapshot, browser_click,
browser_type — each one round trip through the active pipe to the extension.
MIT with Augmentor Resale Restriction. Free personal/business use and modification; resale requires prior written permission from Manolo Remiddi.