What it may solve
Delete one complete closed turn from a DeepSeek Harness session without deleting the session
Imported third-party catalog description; not a Registry verification conclusion.Delete one complete closed turn from a DeepSeek Harness session without deleting the session
Author: hanshenmesen · Sessions & Messages · Catalog snapshot: 2026-09-19Canonical semantic path
Delete one complete closed turn from a DeepSeek Harness session without deleting the session
Imported third-party catalog description; not a Registry verification conclusion.— stars · 297 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 106 stars, 5 commits, 1 forks, and 1 watches; latest commit 2026-08-18.
Conclusion: Resolved npm release 0.1.0, published 2026-08-18, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. 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 observed 1 code capabilities: may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-turn-delete@0.1.0; SHA-256: 57e1025621d0679612660f3f4585cb39642805ba8738dd13e50e8d3daa1bdb28.
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-turn-delete. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-turn-deleteAnalyzed 0.1.0github:hanshenmesen/dsh-turn-deleteExact version not resolved