Feature Request: Support agent-specific plugin configuration for sub-agents

Feature Request: Support agent-specific plugin configuration for sub-agents

Problem

Currently, enabledPlugins in settings applies uniformly to both the main Claude Code agent and all sub-agents spawned via the Task tool. There's no way to:

1. Disable a plugin for the main agent while keeping it available for sub-agents
2. Enable a plugin only for specific custom sub-agents
3. Restrict plugin access at the agent level (like we can with tools)

Use Case

Some plugins (e.g., Figma, Shopify MCP) add significant context overhead via their tools. Users may want to:

• Keep the main agent lean by disabling heavy plugins
• Have specialized sub-agents that enable those plugins only when needed
• Prevent the main agent from using certain plugin tools while delegating to purpose-built sub-agents

Proposed Solution

Allow enabledPlugins configuration at the sub-agent level in sub-agents.md:

---
name: design-agent
description: Agent for Figma design tasks
tools: Read, Write, Bash
enabledPlugins:
  "figma@claude-plugins-official": true
---

And/or add a user-level setting to disable plugins for the main agent only:

{
  "mainAgentPlugins": {
    "figma@claude-plugins-official": false
  },
  "enabledPlugins": {
    "figma@claude-plugins-official": true
  }
}

Benefits

• Reduced context usage for the main agent
• More granular control over plugin exposure
• Consistent with existing tool-level restrictions for sub-agents
• Better separation of concerns between general and specialized agents