Severe performance regression: 2-19 second delay for local slash commands on WSL/Linux

Bug Report: Severe Performance Regression on WSL/Linux

Environment

• Claude Code Version: 1.0.58
• OS: Ubuntu 22.04.5 LTS on WSL2 (Linux DragonL 6.6.87.2-microsoft-standard-WSL2)
• Shell: zsh
• Installation: via npm/scoop (alias to ~/.claude/local/claude)

Problem Description

Severe performance regression affecting ALL slash commands and basic operations on WSL/Linux environments.

Performance Data

$ time claude status
# Output: [normal status response]
~/.claude/local/claude status < /dev/null  2.54s user 0.83s system 17% cpu 19.144 total

Key metrics:

• 19.144 seconds total execution time for a simple local command
• 17% CPU utilization indicating excessive waiting/blocking
• 2-19 second delays for ALL operations including /help, /clear, /status

Symptoms

1. All slash commands affected: /help, /clear, /status all show 1-2 second "Creating..." state
2. Platform-specific: Same version (1.0.58) works normally on Windows
3. Recent regression: This behavior did not exist in previous versions
4. Blocks user interaction: Cannot perform any operations during the delay period

Expected Behavior

Local commands like /status, /help, /clear should execute instantly (<100ms) as they require no network calls or AI processing.

Impact

This makes Claude Code completely unusable for development workflows on Linux/WSL environments due to the severe latency affecting basic operations.

Additional Context

• The delay appears before any actual processing begins
• Shows "Creating... (0s · ↓ 0 tokens · esc to interrupt)" during the delay
• User reports this is a recent issue that wasn't present in earlier versions
• Affects development workflow fluency significantly

Reproduction Steps

1. Install Claude Code 1.0.58 on WSL2/Linux
2. Run any slash command: claude /status or claude /help
3. Observe 2-19 second delay before execution

This appears to be a critical performance regression that needs immediate attention.