danghuangshang
danghuangshang is an openclaw-based multi-agent collaboration system (AI “court”) that dispatches tasks across role-specific agents (e.g., 内阁/六部/都察院 style) via chat platforms like Discord/Feishu and can also do GitHub code review workflows. It provides scripts for installation, regime switching (ming/tang/modern), memory persistence/backup, a web dashboard, and various integrations/tools.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README references webhook signature verification (security update) and includes explicit Discord multi-bot safety guidance (allowBots="mentions"; avoid @everyone). However, provided data does not describe fine-grained authorization scopes, secure storage mechanisms (vault/HSM) beyond config files, or comprehensive threat-model/error-handling for auth failures.
⚡ Reliability
Best When
You want a self-hosted, multi-agent orchestration setup with chat-based triggers (mentions), persistent per-agent memory, and optional GitHub review automation.
Avoid When
You cannot safely run bots/webhooks (webhook signing must be configured; Discord looping must be prevented) or you need a simple single-agent chat API.
Use Cases
- • Multi-agent task delegation and orchestration (e.g., plan → execute → review loops)
- • Discord-based agent collaboration for coding, documentation, and reviews
- • GitHub PR/CI assisted workflows and automated code review
- • Long-running agent memory with backup/restore
- • Running a self-hosted agent “team” with a web dashboard
- • Content generation and structured multi-agent workflows (e.g., Hanlin novel writing template)
Not For
- • A hosted SaaS that requires no self-management (it’s primarily self-hosted)
- • Turnkey enterprise compliance (no explicit compliance/security certifications stated in provided data)
- • Environments where outbound network access to LLM/Discord/Feishu/Notion is prohibited
- • Strictly REST/OpenAPI client integrations without platform-specific event handling
Interface
Authentication
No OAuth-style delegated scopes are described in provided content. Auth is primarily via platform tokens/secrets configured in openclaw/related config. The README mentions webhook signature validation (for security updates) and Discord safety settings (allowBots).
Pricing
Project is MIT licensed and self-hosted; costs primarily come from LLM usage plus hosting.
Agent Metadata
Known Gotchas
- ⚠ Discord multi-bot looping risk: must set allowBots to "mentions" and avoid @everyone to prevent message storms.
- ⚠ Remote installation is not described as idempotent; behavior may depend on existing OpenClaw install state.
- ⚠ Memory persistence requires backups; losing memory is described as effectively irreversible.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for danghuangshang.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.