Unverified50% confidenceFactExact time
The authorization mechanism of dsh-superagent has three layers: the allowlist determines who can initiate, the admission table determines how to handle cases when no one is named, and accounts in the bot list can only produce inferred candidates and cannot initiate explicit requests.
1
Sources
50%
Confidence
Long-term
Relevance
11/4/2026
First Seen
Sources
DeepSeek's Open-Source Agent Teardown: 11,700 Stars but Only One Commit
bilibili翻车老头11/3/2026
Related Entities
Related Claims
UnverifiedSuper Agent requires configuring in advance who can assign tasks and records the permitted processing scope when accepting a task; a sentence added mid-discussion cannot automatically become broader permission.71% similarUnverifiedIn dsh-superagent, the Router is responsible for receiving tasks, determining intent and dispatching, while the Worker is responsible for actually executing time-consuming actions such as code generation and file operations.69% similarUnverifiedIn multi-agent architectures, the spawning and invocation strategy for sub-agents is often determined by internal system algorithms, and the priority of user instructions may be ignored.64% similarUnverifiedIn DSupport, each expert is wrapped as a SubAgentTool, which is just an ordinary tool from the orchestrator's perspective; SubAgentTool receives an agent factory rather than an agent instance, because each agent holds its own history and parallel calls cannot share an instance.63% similarUnverifiedDSH plugins and Agent presets are two different mechanisms: a preset is a packaged system prompt, tool whitelist, permission policy, and workflow template, while a plugin is an extension distributed as an npm package or release package.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1133483API
curl https://kongchang.com/api/v1/knowledge/claims/1133483MCP
get_claim(id=1133483)