zzzgydi/verge-browser
C3Self-hosted browser sandbox for AI agents. Chromium, CDP, Playwright, noVNC/Xpra, persistent sessions & human takeover.
★ 10+ · zzzgydi/verge-browser source on GitHub · this plugin in the registry
zzzgydi/verge-browser is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, executes commands in development tooling the package does not ship, decodes base64 payloads.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can rewrite the system prompt | prompt_surface | systemPrompt |
| executes commands in development tooling the package does not ship | exec_tooling | ×1 in development tooling the package does not ship, e.g. packages/node/scripts/check-package.mjs:2 |
| decodes base64 payloads | base64_decode | ×1 in authored code, e.g. packages/node/src/cli.ts:315 |
| starts a network server in development tooling the package does not ship | net_server_tooling | ×2 in development tooling the package does not ship, e.g. packages/node/scripts/check-package.mjs:38, packages/node/scripts/check-package.mjs:47 |
| reads credential-class env vars | token_env | VERGE_BROWSER_TOKEN |
Tool registrations
0 confirmed registration point(s); analysis is incomplete.
packages/dsh-plugin/src/index.ts:34Context or tools service passed to an unresolved helper
Services it injects
agents browserUse locale sidebarRightTabs slots systemPrompt tools workingDirectory
Environment variables it reads
VERGE_DSH_CONFIG VERGE_BROWSER_URL VERGE_BROWSER_TOKEN
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.