dsh-plugin-installer

Adding a persistent plugin to a DSH profile looks like a single pnpm add, but under the hood it mutates package.json, cordis.patch.yml, settings.yaml, and more. A mistaken install, an uninstall that removes a package other configs still reference, or a new plugin that registers a tool with an empty parameters object can silently pass registration yet trigger Invalid schema for function X on every single LLM turn—breaking every conversation. Manually rolling back is tedious, error-prone, and wipes your session context.

dsh-plugin-installer wraps the full lifecycle into three model tools: install_plugin, uninstall_plugin, and restart_dsh. An agent can now run backup, install or uninstall, restart, a tool-schema health audit, automatic rollback on any failure, and seamless conversation resume without ever issuing a raw shell command. The schema audit deserves special attention: after the port comes up, the plugin enumerates every registered tool and verifies that its parameters conform to a valid JSON Schema with a top-level type of object, catching the silent corruption that passes registration but makes the LLM API reject every subsequent call. The uninstall path mirrors install protection with equal rigor—on failure it restores the backup and re-installs the removed plugin, not just copies files back. Updating a local file: dev plugin triggers an automatic remove-then-add cycle to bypass pnpm's stale-copy caching when the version number is unchanged.

It suits three audiences well: agent users who frequently install or update persistent DSH plugins, especially in local development loops; developer teams that want the LLM to manage plugins autonomously while keeping a reliable safety net against broken environments; and anyone who needs to drop a plugin in mid-session and continue the conversation immediately rather than manually restarting and losing context. By default a single-use elevation approval is required outside danger-full-access sandboxes, and an allowProfiles whitelist can further restrict which profiles are affected.