Adds a Settings "Loop engine" dropdown that switches which agent loop engine drives sessions — the built-in in-process driver or a hosted Claude Code, Codex, Pi, or Kimi Code engine — with no changes to the harness; the Kimi Code engine streams assistant text and thinking.
Author: kuun993 · Development & Runtime · Catalog snapshot: 2026-09-19Canonical semantic path
Adds a Settings "Loop engine" dropdown that switches which agent loop engine drives sessions — the built-in in-process driver or a hosted Claude Code, Codex, Pi, or Kimi Code engine — with no changes to the harness; the Kimi Code engine streams assistant text and thinking.
Imported third-party catalog description; not a Registry verification conclusion.4 stars · 1897 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.
Installation and startup verification has not been run.
Dependency audit has not been run.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The static risk scan could not complete because package validation did not pass.
Conclusion: Core package structure passed, but an optional export path is missing.
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-loop-engine. 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-loop-engineAnalyzed 0.1.5-rc3github:kuun993/dsh-loop-engineExact version not resolved