Iwctwbh/dsh-flowglass

C3

流镜 Flowglass — DeepSeek Harness session flowgraph,实时可视化消息、工具组、子代理分支与步骤详情。

★ 10+ · Iwctwbh/dsh-flowglass source on GitHub · this plugin in the registry

Iwctwbh/dsh-flowglass is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, can spawn subprocesses, executes system commands.

Installable plugin — declares a dsh.bundle manifest

What it can do

CapabilityFlagEvidence
patches the dsh runtimeruntime_patch./flowglass/cordis.patch.yml
can rewrite the system promptprompt_surfacesubprocess, systemPrompt
can spawn subprocessessubprocess_serviceinject: subprocess
executes system commandsexec×39 in authored code, e.g. smoke.mjs:6, smoke.mjs:6
uses eval / new Functioneval×35 in authored code, e.g. loader.js:15, smoke/sim-aiassist.cjs:91
decodes base64 payloadsbase64_decode×1 in authored code, e.g. plugins/selfview/tool.js:151
starts a network server in development tooling the package does not shipnet_server_tooling×2 in development tooling the package does not ship, e.g. scripts/test-flowglass-stable.mjs:21, scripts/test-flowglass-stable.mjs:22
reads credential-class env varstoken_envJIRA_ISSUE_KEY, JIRA_TOKEN

Services it injects

credentials fs remote sessionQuery sessions slots subprocess systemPrompt tb-pill-other timer tokenMeter toolboxNativeBridgeDynamicToolbox toolboxRegistryDynamicToolbox tools

Hooks it attaches

agent/session-start llm/adapters-updated theme/change

Outbound domains

your-team.atlassian.net x.org api.example.com

Environment variables it reads

JIRA_BASE_URL JIRA_EMAIL JIRA_TOKEN JIRA_ARCHIVE_ROOT JIRA_ISSUE_KEY DSH_INSTALL_ROOT PREFIX JIRA_ATTACH_URL JIRA_ATTACH_NAME JIRA_ISSUE_FILE

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.