A persistent agent team for long-running collaboration in DeepSeek Harness: durable agent identities, per-project Workspaces, responsibility-bearing Channels, and Task Threads chaining session agents.
Author: wowyuarm · Workflow & Automation · Catalog snapshot: 2026-09-19Canonical semantic path
A persistent agent team for long-running collaboration in DeepSeek Harness: durable agent identities, per-project Workspaces, responsibility-bearing Channels, and Task Threads chaining session agents.
Imported third-party catalog description; not a Registry verification conclusion.31 stars · 2827 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.
Source structure has not been analyzed.
Repository metadata has not been analyzed.
npm release metadata has not been analyzed.
Conclusion: Compatibility verification did not pass: the DSH process exited during startup. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan found 5 characteristics that need attention: contains credential or token handling code, may execute dynamically constructed code, may read environment variables, may create or modify files, may access the network. This is a bounded automated observation, not a determination of malicious intent.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: @wowyuarm/dsh-agent-team@0.1.13; SHA-256: 822212a3cecbef46b722b5ace40494d6c5164076ac215e4289517946e9a9c7c9.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention dsh-agent-team. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
@wowyuarm/dsh-agent-teamAnalyzed 0.1.13github:wowyuarm/dsh-agent-teamExact version not resolved