What problem does it solve?
Claude Code loads every installed plugin into the assistant context, which increases token use and noise before you start working. forge-profiles solves this by letting you define and switch between named plugin sets so only relevant plugins and MCP servers are active for the task at hand.
Core Features & Use Cases
- Profile storage: Profiles are stored in .claude/settings.local.json under pluginConfigs["forge-profiles@dev-forge"].options.profiles so they remain personal and project-local.
- Create, list, switch: Create profiles from the current configuration, list available profiles with descriptions, and switch profiles while previewing the diff of installs/removals.
- Preserve runtime config: Switching computes diffs for plugins and mcpServers while preserving permissions, environment variables, and server definitions.
- Use cases: Keep a lean "daily" set for everyday coding, a "plugin-dev" set for extension development, or a "review" set with only analysis tools.
Quick Start
Switch my active plugins to the "daily" profile and show the install/remove diff before I run /reload-plugins.