oceanbase/powercontext
C3Agent memory: long-term memory & agent memory handoff. Claude Code & Codex.
★ 1.5k · oceanbase/powercontext source on GitHub · this plugin in the registry
oceanbase/powercontext is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, gates tool execution, executes system commands.
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, tools/pre-execute |
| gates tool execution | tool_gate | hook: tools/pre-execute |
| executes system commands | exec | ×14 in authored code, e.g. desktop/scripts/generate.mjs:26, desktop/scripts/generate.mjs:129 |
| eval in build output only | eval_bundled | ×1 in build output only, e.g. src/powercontext/server/dashboard/static/vendor/htmx.min.js:1 |
| starts a network server | net_server | ×4 in authored code, e.g. integrations/dsh/plugins/powercontext/scripts/e2e-server.mjs:46, integrations/dsh/plugins/powercontext/scripts/e2e-server.mjs:47 |
| reads credential-class env vars | token_env | POWERCONTEXT_REPLAY_TOKEN, POWERCONTEXT_ZCODE_AUTHORIZATION |
Tool registrations
0 static tool registration point(s).
Services it injects
agents commands skills systemPrompt tools
Hooks it attaches
agent/pre-step tools/pre-execute
Outbound domains
popper.js.org svgjs.dev
Environment variables it reads
ZCODE_PLUGIN_DATA POWERCONTEXT_OPENCODE_ACTIVATION_PROBE_PATH POWERCONTEXT_OPENCODE_ACTIVATION_PROBE_NONCE GITHUB_OUTPUT ZCODE_SESSION_ID POWERCONTEXT_ZCODE_SERVER_URL POWERCONTEXT_BROWSER_URL POWERCONTEXT_BROWSER_OUTPUT POWERCONTEXT_REPLAY_TOKEN POWERCONTEXT_BROWSER_SCOPE
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.