/plugin command causes 100% CPU freeze (v2.1.27)
Resolved 💬 10 comments Opened Jan 31, 2026 by TPG24 Closed Mar 2, 2026
Environment
- Claude Code version: 2.1.27
- OS: macOS Darwin 25.2.0 (arm64, Apple Silicon)
- Shell: zsh
Bug Description
Typing /plugin in Claude Code causes the process to immediately spike to 100% CPU and freeze indefinitely. The process must be killed with kill -9.
Steps to Reproduce
- Start Claude Code:
claude --dangerously-skip-permissions - Type
/pluginand press Enter - Process immediately goes to 100% CPU and becomes unresponsive
Expected Behavior
The plugin menu should appear showing installed/available plugins.
Actual Behavior
- Process spikes to 100% CPU
- UI becomes completely frozen
- No output is displayed
- Must force kill with
kill -9 <PID>
Diagnostic Steps Taken
- Tested with all plugins enabled (7 plugins): Freezes
- Tested with some plugins disabled: Freezes
- Tested with ALL plugins disabled: Still freezes
This confirms the issue is in Claude Code itself, not in any plugin.
Plugin Configuration Tested
{
"enabledPlugins": {
"ciq@secondbrain": false,
"eng@secondbrain": false,
"saga@secondbrain": false,
"setup@secondbrain": false,
"superpowers@claude-plugins-official": false,
"superpowers@superpowers-marketplace": false,
"code-review@claude-plugins-official": false
}
}
Even with this configuration (all plugins disabled), /plugin causes 100% CPU freeze.
Process Information During Freeze
tonygiamboy 9153 99.1% 1.2 508934272 451728 ?? R+ claude --dangerously-skip-permissions
Workaround
Avoid using the /plugin command. Skills can still be invoked via Skill() tool or /skillname syntax.
Additional Context
- Multiple concurrent frozen sessions were observed (3 sessions at 99-100% CPU simultaneously)
- The freeze appears to be an infinite loop (100% CPU, not I/O wait)
- Other slash commands may work fine; specifically
/plugintriggers this
This issue has 10 comments on GitHub. Read the full discussion on GitHub ↗