Feature Request: CLI Support for Plugin Enable/Disable #11743

Use Case

In my use case, I found that when using plugins like oh-my-opencode, token consumption can increase significantly. It’s a good plugin, but it doesn’t necessarily need to be enabled all the time. Currently, there’s no quick way to temporarily disable a plugin to save tokens without manually editing configuration files or uninstalling it.

Proposal

I'd like to contribute a PR to add plugin management capabilities via both CLI and interactive Slash Commands.

Interactive CLI

• /plugin list: List plugins status in the chat.
• /plugin disable <name>: Disable a plugin (updates config).
• /plugin enable <name>: Enable a plugin.

Design

1. Config: Add disabled_plugins: string[] to opencode.json.
2. Logic: Skip loading plugins present in the disabled_plugins list.

If the team agrees with this approach, I am happy to submit a PR implementing this.