relayloom

RelayLoom bridges DeepSeek Harness agents to the DingTalk Stream protocol, solving a common gap: agents that can only passively receive a one-way group notification instead of completing a full receive-ACK-reply cycle in direct messages or group mentions. It binds the official dingtalk-stream Node SDK at the protocol layer, sends the callback ACK before asynchronous model work settles, deduplicates retries by msgId to prevent storm amplification, and isolates conversations by sender and context so parallel users never bleed into each other's sessions.

Security is the backbone of the design. The bundle ships disabled by default; enabling it requires a non-empty staff-id allowlist. Credentials are read exclusively from named environment variables, never from YAML or shell history. Every sessionWebhook reply is pinned to an exact HTTPS host, 302 redirects are denied, response bodies are size-capped, and timeouts are enforced. The text-based /approve and /reject flow is single-use, expiring, and bound to the original sender and conversation, acting as a safe fallback rather than a claim that interactive card rendering works today.

This plugin is aimed at developers who are building agent workflows on DeepSeek Harness and want a conversation entry point on an internal DingTalk robot. It is not a managed production bot or a marketplace product; it is a default-off, auditable interoperability layer that lets you validate the protocol round trip in a local or intranet environment before deciding whether to roll it out to a real tenant.