-
Notifications
You must be signed in to change notification settings - Fork 19
Description
ocx self uninstall says it succeeded, and warned about not removing a directory with non-ocx content, which is fine.
It didn't remove the configuration which ocx placed in that file, which is undesirable behavior.
Even if it mirrors Cargo's processes, the difference between Cargo and OCX is that when Cargo is removed the remaining binaries are self-contained and you don't have to do anything to not use them. With what OCX leaves behind, opencode is still configured and operating in a state which OCX managed. For example, after installing kdcokenny/opencode-workspace and uninstalling ocx, the MCP servers and permissions applied by OCX are still in place.
Sure, there's complexity in implementing an uninstallation process which removes just what OCX managed and not anything user-configured in the meantime, but there's no warning about this behavior either. Just one user's perspective, but managers-of-things that change the thing's default behavior should be careful about how they uninstall everything they are capable of installing. As an aside, I can't help but notice that there's no ocx remove to accompany ocx add 😅