wushi2333/dsh-computer-use_codex-style
C3Codex-style Computer Use for DeepSeek Harness: the official window2 13-method desktop surface plus Chromium automation, a visible overlay with Esc interrupt, per-app approvals and bundled skills. Wind
★ 10+ · wushi2333/dsh-computer-use_codex-style source on GitHub · this plugin in the registry
wushi2333/dsh-computer-use_codex-style is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, executes system commands, 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 system commands | exec | ×94 in authored code, e.g. parity/atomic-cursor-check.mjs:1, parity/atomic-cursor-check.mjs:1 |
| decodes base64 payloads | base64_decode | ×2 in authored code, e.g. parity/pill-capture-mask.mjs:126, src/tool.js:838 |
Services it injects
dshComputerUse sessions systemPrompt tools
Hooks it attaches
probe/event session/disposed session/event tools/result
Environment variables it reads
DSH_HOME CODEX_HOME LOCALAPPDATA PYTHON CODEX_CLI_PATH USERPROFILE DSH_COMPUTER_USE_HELPER PYTHONPATH DSH_CU_HELPER DSH_CU_EXPERIENCE_DIR
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.