DeepSeek Super-Agent prototype
Inspect research code for permission-scoped GitHub coding work.
Documentation reviewed
Can I use this for my work?
dsh-superagent is research code packaged for DeepSeek Harness. It listens to one GitHub repository and optionally Feishu, starts permitted work in separate sessions and replies in the original thread. Its README explicitly distinguishes the prototype from an official DeepSeek product and production-ready software. Hosting, model access and account setup remain separate.
- Availability
- Available. Available research source, not a GA product. The published implementation differs from the internal system and design essay.
- How to use it
- Library / CLI. Inspect source and generated configuration before installing or executing anything.
- Processing and data
- Local and cloud options. Repository content, threads and configured credentials reach the selected agent host and providers. Review permissions before use.
- Costs and limits
- MIT source; model, hosting and connected-service costs remain separate.
- Outputs
- Work sessions, thread replies and proposed pull requests; no task completion guarantee.
ASE has not installed or audited this prototype. Review the research source and its permissions before use; no production-support or security guarantee is established.
Compare these facts with another tool →
Publisher documentation was reviewed. ASE has not independently tested this workflow, its outputs, billing, privacy controls or accessibility.
Researchers evaluating permission-scoped coding automation in an isolated environment.
You need supported production software or assume the prototype matches DeepSeek's internal system.
About DeepSeek Super-Agent prototype
dsh-superagent is research code packaged for DeepSeek Harness. It listens to one GitHub repository and optionally Feishu, starts permitted work in separate sessions and replies in the original thread. Its README explicitly distinguishes the prototype from an official DeepSeek product and production-ready software. Hosting, model access and account setup remain separate.