loopwithai/LoopWithAI
C3Multi-agent DeepSeek Harness workbench with switchable Pi, OpenAI Codex, Claude Code, and native DeepSeek Agent Loops.
★ 1+ · loopwithai/LoopWithAI source on GitHub · this plugin in the registry
loopwithai/LoopWithAI is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It can rewrite the system prompt, executes system commands, uses eval / new Function, decodes base64 payloads.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| can rewrite the system prompt | prompt_surface | systemPrompt, webServer, system-prompt/assemble |
| executes system commands | exec | ×9 src, e.g. apps/harness-web/scripts/dev.ts:1, apps/harness-web/scripts/dev.ts:35 |
| uses eval / new Function | eval | ×3 src, e.g. vendor/cordis/schemastery/src/index.ts:261, vendor/cordis/loader/src/config/utils.ts:5 |
| decodes base64 payloads | base64_decode | ×2 src, e.g. vendor/cordis/cosmokit/src/types.ts:56, vendor/cordis/cosmokit/src/types.ts:57 |
| starts a network server | net_server | ×1 src, e.g. apps/harness-web/scripts/dev.ts:14 |
| reads credential-class env vars | token_env | DEEPSEEK_API_KEY |
| ships no manifest | no_manifest | uses 12 services, 3 tool regs, no manifest |
Services it injects
agents invariants llm loader networkProxy sessions settings systemPrompt timer tools webServer workspaceRegistry
Hooks it attaches
agent/status credentials/updated event internal/config internal/dispatch internal/plugin internal/status internal/update llm/adapters-updated llm/stream loader/entry-init loader/partial-dispose loader/patch-context session/created session/disposed session/event session/flush settings/updated system-prompt/assemble
Outbound domains
api.deepseek.com stackoverflow.com esbuild.github.io
Environment variables it reads
LOOPWITHAI_VITE_PORT CORDIS_SHARED DEEPSEEK_API_URL DEEPSEEK_API_KEY DEEPSEEK_MODEL LOOP_DATA_DIR CODEX_BINARY LOOPWITHAI_UI_DEV_URL
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.