plastic-labs/dsh-honcho
C3Honcho integration for the DeepSeek Harness
★ 10+ · plastic-labs/dsh-honcho source on GitHub · this plugin in the registry
plastic-labs/dsh-honcho 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, reads credential-class env vars.
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, system-prompt/assemble |
| executes system commands | exec | ×3 in authored code, e.g. src/git.ts:9, src/git.ts:9 |
| reads credential-class env vars | token_env | HONCHO_API_KEY |
Tool registrations
4 static tool registration point(s).
src/index.ts:437tools.registersrc/tools.ts:61tool factorysrc/tools.ts:90tool factorysrc/tools.ts:120tool factory
Services it injects
systemPrompt tools
Hooks it attaches
agent/created agent/pre-step session/event system-prompt/assemble
Outbound domains
api.honcho.dev app.honcho.dev
Environment variables it reads
HONCHO_CONFIG_DIR HONCHO_API_KEY HONCHO_BASE_URL HONCHO_PEER_NAME USERNAME HONCHO_HOST
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.