dsh
| plugin-dsh — Served by | plugin-dsh |
| plugin-dsh — Placement | compiled-in (in-process) |
| plugin-dsh — Version | 2026.226.1600 |
| plugin-dsh — Served by | plugin-dsh |
| plugin-dsh — Placement | compiled-in (in-process) |
| plugin-dsh — Version | 2026.226.1600 |
| plugin-dsh — Served by | plugin-dsh |
| plugin-dsh — Placement | compiled-in (in-process) |
| plugin-dsh — Version | 2026.226.1600 |
dsh is a command word served by 3 plugin candies — plugin-dsh and plugin-dsh and plugin-dsh — at different points in the command tree. Both are real invocations; charly --help prints which is which.
About plugin-dsh, which serves it
Section titled “About plugin-dsh, which serves it”The charly dsh management CLI for a deployed deepseek-harness (dsh)
box PLUS the declarative dsh: check verb — a COMPILED-IN
command:dsh + verb:dsh plugin. charly dsh status --box <name>
reports the dsh version and web UI health in the box; profile list
lists the profiles under $DSH_HOME/profiles; plugin list --profile <name> lists a profile’s plugins. The command reaches a DEPLOYED box
over the reverse channel via the plugin-cmd pattern (the
“pod-lifecycle” host-builder’s op=“cmd” — compiled-in placement
required). The dsh: check verb is the declarative in-box probe
counterpart, authored as a check: step (dsh: version,
web-running, profile-list, plugin-list): it runs dsh commands
INSIDE the venue via cc.Exec().RunCapture — the one place plugin-dsh
diverges from plugin-agentteams’ host-based cc.ResolveEndpoint (the
loopback-bound web UI is probed in-box on 127.0.0.1:3080).
About plugin-dsh, which serves it
Section titled “About plugin-dsh, which serves it”The charly dsh management CLI for a deployed deepseek-harness (dsh)
box PLUS the declarative dsh: check verb — a COMPILED-IN
command:dsh + verb:dsh plugin. charly dsh status --box <name>
reports the dsh version and web UI health in the box; profile list
lists the profiles under $DSH_HOME/profiles; plugin list --profile <name> lists a profile’s plugins. The command reaches a DEPLOYED box
over the reverse channel via the plugin-cmd pattern (the
“pod-lifecycle” host-builder’s op=“cmd” — compiled-in placement
required). The dsh: check verb is the declarative in-box probe
counterpart, authored as a check: step (dsh: version,
web-running, profile-list, plugin-list): it runs dsh commands
INSIDE the venue via cc.Exec().RunCapture — the one place plugin-dsh
diverges from plugin-agentteams’ host-based cc.ResolveEndpoint (the
loopback-bound web UI is probed in-box on 127.0.0.1:3080).
About plugin-dsh, which serves it
Section titled “About plugin-dsh, which serves it”The charly dsh management CLI for a deployed deepseek-harness (dsh)
box PLUS the declarative dsh: check verb — a COMPILED-IN
command:dsh + verb:dsh plugin. charly dsh status --box <name>
reports the dsh version and web UI health in the box; profile list
lists the profiles under $DSH_HOME/profiles; plugin list --profile <name> lists a profile’s plugins. The command reaches a DEPLOYED box
over the reverse channel via the plugin-cmd pattern (the
“pod-lifecycle” host-builder’s op=“cmd” — compiled-in placement
required). The dsh: check verb is the declarative in-box probe
counterpart, authored as a check: step (dsh: version,
web-running, profile-list, plugin-list): it runs dsh commands
INSIDE the venue via cc.Exec().RunCapture — the one place plugin-dsh
diverges from plugin-agentteams’ host-based cc.ResolveEndpoint (the
loopback-bound web UI is probed in-box on 127.0.0.1:3080).
charly --help prints the command tree, including where each dsh is invoked and under which parent.