loopx-project/loopx

C3

A control plane with a durable state kernel for long-horizon agents and teams. Keep work moving and improving across sessions, with less human attention.

★ 6.1k · loopx-project/loopx source on GitHub · this plugin in the registry

loopx-project/loopx is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, decodes base64 payloads, starts a network server.

Installable plugin — declares a dsh.bundle manifest

What it can do

CapabilityFlagEvidence
patches the dsh runtimeruntime_patch./cordis.patch.yml
executes system commandsexec×45 in authored code, e.g. scripts/chat_bundle_launcher.mjs:10, scripts/chat_bundle_launcher.mjs:10
decodes base64 payloadsbase64_decode×3 in authored code, e.g. demo/workspace/readme-hero/render.mjs:137, loopx/control_plane/coordination/nokv_jsonl_transport.ts:82
starts a network servernet_server×2 in authored code, e.g. loopx/control_plane/effect_runtime_server.ts:141, loopx/control_plane/effect_runtime_server.ts:278
reads credential-class env varstoken_envLOOPX_EFFECT_RUNTIME_TOKEN

Services it injects

agents commands connection locale loopxBootstrap slots

Hooks it attaches

agent/created agent/disposed agent/error agent/inbox/claimed agent/inbox/discarded agent/inbox/inserted agent/pre-step agent/session-start agent/status connection/reset session/created session/disposed session/event

Outbound domains

loopx-project.github.io www.sitemaps.org bouwenzhou.github.io wanli-lee.github.io loopx-usage-collector.huangrt01.workers.dev policies.google.com www.googletagmanager.com www.google-analytics.com schema.org www.apache.org

Environment variables it reads

LOOPX_BIN LOOPX_OPENCODE2_STATE_DIR DSH_BIN LOOPX_EFFECT_RUNTIME_TOKEN XDG_STATE_HOME LOOPX_OPENCODE_STATE_DIR LOOPX_PI_STATE_DIR LOOPX_SITE_BASE PYTHON_BIN LOOPX_ACCEPTANCE_SCOPE_SCREENSHOT_DIR

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.