WindyPro-rourou/dsh-logcat
C2Android Logcat viewer for the DeepSeek Harness (DSH) Web GUI: auto-connect adb devices, live logcat stream with level/keyword filters, pause/clear/export, plus the logcat_recent agent tool.
★ 10+ · WindyPro-rourou/dsh-logcat source on GitHub · this plugin in the registry
WindyPro-rourou/dsh-logcat is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, command execution in build output only, executes commands in development tooling the package does not ship.
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, webServer |
| command execution in build output only | exec_bundled | ×4 in build output only, e.g. lib/index.js:17, lib/index.js:323 |
| executes commands in development tooling the package does not ship | exec_tooling | ×5 in development tooling the package does not ship, e.g. tools/injector/build.mjs:15, tools/injector/build.mjs:15 |
| base64 decoding in build output only | base64_decode_bundled | ×1 in build output only, e.g. lib/client.js:1343 |
Services it injects
slots systemPrompt tools webServer
Outbound domains
mirrors.ustc.edu.cn dl.google.com
Environment variables it reads
ANDROID_HOME ANDROID_SDK_ROOT
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.