omdsh-dev/dsh-browser
C3Chrome sidebar extension that lets DeepSeek Harness operate your browser directly, no vision capabilities required. 一款 Chrome 侧边栏扩展程序,可让 DeepSeek Harness 直接操控您的浏览器,无需视觉能力。
★ 1.0k · omdsh-dev/dsh-browser source on GitHub · this plugin in the registry
omdsh-dev/dsh-browser is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, decodes base64 payloads, starts a network server.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×10 in authored code, e.g. scripts/smoke-browser.mjs:2, scripts/smoke-browser.mjs:45 |
| decodes base64 payloads | base64_decode | ×2 in authored code, e.g. extensions/dsh-browser/src/background/tools.ts:1154, packages/browser/bridge-browser/src/screenshot-tools.ts:77 |
| starts a network server | net_server | ×6 in authored code, e.g. scripts/smoke-browser.mjs:60, scripts/smoke-browser.mjs:70 |
Tool registrations
29 static tool registration point(s).
benchmark/plugin/playwright-browser.mjs:422tools.registerpackages/browser/bridge-browser/src/devtools-tools.ts:90tools.registerpackages/browser/bridge-browser/src/devtools-tools.ts:104tool factorypackages/browser/bridge-browser/src/devtools-tools.ts:122tool factorypackages/browser/bridge-browser/src/devtools-tools.ts:154tool factorypackages/browser/bridge-browser/src/devtools-tools.ts:170tool factorypackages/browser/bridge-browser/src/devtools-tools.ts:185tool factorypackages/browser/bridge-browser/src/devtools-tools.ts:198tool factorypackages/browser/bridge-browser/src/devtools-tools.ts:210tool factorypackages/browser/bridge-browser/src/devtools-tools.ts:228tool factorypackages/browser/bridge-browser/src/devtools-tools.ts:243tool factorypackages/browser/bridge-browser/src/screenshot-tools.ts:82tool factorypackages/browser/bridge-browser/src/screenshot-tools.ts:163tools.registerpackages/browser/bridge-browser/src/tools.ts:125tools.registerpackages/browser/bridge-browser/src/tools.ts:144tool factorypackages/browser/bridge-browser/src/tools.ts:177tool factorypackages/browser/bridge-browser/src/tools.ts:194tool factorypackages/browser/bridge-browser/src/tools.ts:211tool factorypackages/browser/bridge-browser/src/tools.ts:229tool factorypackages/browser/bridge-browser/src/tools.ts:242tool factorypackages/browser/bridge-browser/src/tools.ts:253tool factorypackages/browser/bridge-browser/src/tools.ts:274tool factorypackages/browser/bridge-browser/src/tools.ts:286tool factorypackages/browser/bridge-browser/src/tools.ts:297tool factorypackages/browser/bridge-browser/src/tools.ts:315tool factorypackages/browser/bridge-browser/src/tools.ts:332tool factorypackages/browser/bridge-browser/src/tools.ts:373tool factorypackages/browser/bridge-browser/src/tools.ts:382tool factorypackages/browser/bridge-browser/src/tools.ts:400tool factory
Services it injects
agents connection locale slots tools typertGateway webServer
Hooks it attaches
agent/created
Outbound domains
api.example.com
Environment variables it reads
EXT_TARGET CHROMIUM_PATH PLAYWRIGHT_CHROMIUM_PATH BENCHMARK_SITE_PORT
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.