What it may solve
Ownership-checked tools and HTTP routes to list, release and permanently delete subagent sessions, with automatic web UI refresh after deletion.
Imported third-party catalog description; not a Registry verification conclusion.dsh-plugin-subagent-delete
Automated evidence availableOwnership-checked tools and HTTP routes to list, release and permanently delete subagent sessions, with automatic web UI refresh after deletion.
Author: heiheiha798 · Sessions & Messages · Catalog snapshot: 2026-09-19Canonical semantic path
Sessions & MemorySession Lifecycle ManagementSession Deletion & Recycle Bin
One primary path; alternate capabilities remain separate.Sources and public signals
heiheiha798/dsh-plugin-subagent-delete
1 stars · — downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19What can currently be confirmed
Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Source structure
Conclusion: The source structure check completed without finding a structural issue.
Repository health
Conclusion: The GitHub repository is reachable and not archived. Public data: 2 stars, 10 commits, 0 forks, and 0 watches; latest commit 2026-08-21.
npm release
Conclusion: This plugin has no npm package source, so this item does not apply.
DSH compatibility
Conclusion: Compatibility verification did not pass: the bounded compatibility check did not pass. Test environment: DSH 0.1.6-alpha.2, web profile.
Dependency audit
Conclusion: The dependency audit did not produce a complete report.
Functional verification
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Static risk scan
Conclusion: The bounded static scan found none of its predefined risk signals. This is not proof of safety.
Package integrity
Conclusion: Package structure or integrity validation did not pass.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Continue with the latest plugin manager
Describe your task in a DSH conversation and mention dsh-plugin-subagent-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.
Sources available for local inspection
- GitHub source
github:heiheiha798/dsh-plugin-subagent-deleteExact version not resolved