Feature Request: Better Plugin Configuration Experience

Ideas Feature Requests
1

Feature request for product/service

Cursor IDE

Describe the request

I’ve been using plugins a lot lately, and they’ve become a really important part of my workflow.

One thing that feels missing right now is a way to configure plugins directly inside Cursor. For simple plugins this is manageable, but once a plugin has multiple settings or modes, configuration becomes difficult to organize.

What would be really useful is not only a settings UI, but support for dynamic configuration based on previous selections.

A lot of plugin settings naturally depend on other settings. For example:

  • only show subagentConfig if agentMode is enabled
  • show advanced orchestration settings only when executionMode is set to "advanced"

A more concrete example:

  • if agentType = "root", show high-level planning and coordination settings
  • if agentType = "subagent", show task scope, communication, and delegation settings

Or:

  • if workflowMode = "single", keep configuration minimal
  • if workflowMode = "multi-agent", expose routing and dependency settings

Without this kind of logic, plugin settings either become cluttered with options that don’t apply to the current mode, or plugin authors have to push users toward editing config files manually.

A schema-based settings system could solve this by allowing plugins to define:

  • field types such as boolean, string, number, enum, arrays, and objects
  • default values
  • validation rules
  • conditional visibility rules

Something like:

{
  "delegationStrategy": {
    "type": "enum",
    "visibleWhen": {
      "agentType": "root"
    }
  }
}

or

{
  "taskScope": {
    "type": "string",
    "visibleWhen": {
      "agentType": "subagent"
    }
  }
}

This would make plugin setup much cleaner, reduce friction, and allow more advanced plugins to feel properly integrated into Cursor instead of depending on manual configuration.

Plugins already feel an important Cursor’s feature. A flexible native configuration system would make the overall experience much smoother for both plugin developers and users without having to use sidecars.