yangbobo2021/relay-dsh-plugin-codex
C3Codex integration plugin for DeepSeek Harness, providing native Codex conversations powered by the Codex App Server, with workspace, terminal, approval, and DSH tool support.
★ 10+ · yangbobo2021/relay-dsh-plugin-codex source on GitHub · this plugin in the registry
yangbobo2021/relay-dsh-plugin-codex is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, decodes base64 payloads, 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 |
| executes system commands | exec | ×4 in authored code, e.g. app-server-client.mjs:1, app-server-client.mjs:155 |
| decodes base64 payloads | base64_decode | ×1 in authored code, e.g. codex-image.js:69 |
| reads credential-class env vars | token_env | RELAY_CODEX_IMPORT_TOKEN |
Services it injects
agents approval attachments connection llm locale sessionPersistence sessionTitle sessions settingsScope slots theme tools typert userQuestions webServer workspaceRegistry workspaces
Hooks it attaches
agent-preset/selected agent/created agent/disposed llm/stream
Environment variables it reads
RELAY_CODEX_IMPORT_TOKEN CODEX_HOME CODEX_PRIMARY_RUNTIME_ROOT RELAY_CODEX_LINK_PATH DSH_HOME
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.