plugin-uninstall

To safely uninstall an EvoNexus plugin, the process removes installed agent, rule, and command documents, clears heartbeats and hook handlers, and runs uninstall SQL to revert the workspace state via the API.

When you remove a plugin, the uninstall SQL often drops plugin-managed table data. The process requires explicit confirmation to prevent accidental data loss and suggests exporting data or disabling the plugin as alternatives.

Plugin uninstall handles dependencies by resolving the plugin slug and executing reverse-order dependency rollback, ensuring that dependent components are properly managed before completely removing the target plugin files.

When deleting a plugin via the API, the uninstall process safely handles HTTP 404, 409, and 500 error states, managing issues like missing plugins, conflicts, or internal server errors during the deletion request.

Yes, you can disable a plugin instead of fully uninstalling it. Disabling avoids dropping plugin-managed table data, making it a safer alternative if you want to prevent data loss while stopping the plugin's runtime routines.

Yes, uninstalling a plugin removes Claude hook handlers and clears heartbeats. The process executes pre and post uninstall hook scripts to ensure operational routines and workspace artifacts are completely cleaned up.