dsh-cloak

Every time your agent reads a .env file, a cloud CLI dump, or a log tail, the API keys, database connection strings, and webhook URLs inside flow straight into the conversation context and ride along with every request sent to your model provider. Redacting at export time is too late — the secret has already left your machine while the agent was working. dsh-cloak closes that window: it detects credentials in successful tool results and replaces them with opaque placeholders before they ever reach the model, so the task continues seamlessly while the secret stays put.

It ships 24 high-precision built-in signatures spanning AWS, Aliyun, GCP, OpenAI, Anthropic, GitHub, Slack, Stripe, and more, plus key-name heuristics (password, secret, api_key, …) that catch unknown formats across .env, JSON, and YAML, and a JSON file for custom regex rules. Matched values are stored solely in an in-memory, agent-scoped vault — they never appear in session logs, audit events, or API responses. A restart makes old placeholders intentionally unrestorable. On scanner faults the plugin fails open, so a broken rule file never turns a successful tool call into an error.

Built for developers and ops teams who run agents in multi-credential environments. Whether your workflow touches a dozen cloud providers or a handful of internal webhooks, dsh-cloak stands up a lightweight context firewall between tool execution and model reasoning with zero runtime dependencies, relying only on Node builtins and the DSH host packages.