[Feature Request] Add CLI flags to enable/disable plugins at startup

Description:

Currently there's no way to enable or disable specific plugins when launching
Claude Code from the command line. The only options are:

• Managing plugins interactively within a session (/plugin enable|disable)
• Manually editing settings.json before launching

Proposed flags:

  claude --enable-plugin plugin-name@marketplace
  claude --disable-plugin plugin-name@marketplace

Use cases:

• Quickly start a session without a plugin that conflicts with the current task
• Enable a plugin only for specific projects/workflows without changing global

settings

• Scriptable CI/automation setups where different plugin configurations are needed

per invocation

• Temporary toggling without modifying persistent config files

Comparison: This is analogous to how --mcp-config and --disallowedTools already
allow per-session control over MCP servers and tools. Plugins should have the same
level of CLI configurability.Add CLI flags to enable/disable plugins at startup

Environment Info

• Platform: darwin
• Terminal: waveterm
• Version: 2.1.44
• Feedback ID: c16a9b87-b25d-43ee-85eb-769c7b633519