Appearance
Troubleshooting Guide
Problems, symptoms, and solutions organized by issue type.
Fresh 🌱Quick Symptom Lookup
| Symptom | Likely Cause | Quick Fix |
|---|---|---|
| Teammates won't appear | Task too simple OR not enabled | Enable agent teams (SOP-001) |
| Permission denied | Permissions not granted | Pre-approve or use --dangerously-skip-permissions |
| Messages not arriving | Teammate offline | Check Shift+Down, respawn if needed |
| Split panes broken | tmux not installed | Install tmux OR use in-process mode |
| Team stuck on cleanup | Teammates still running | Shut down each teammate first |
| Tasks not updating | UI lag | Refresh view or tell lead to check |
| Ctrl+T not working | Wrong mode | Verify in lead session (not teammate) |
| Can't exit session | Escape not working | Try Escape twice, or Ctrl+C |
Enabling Agent Teams
Problem: "Agent teams feature not enabled"
Symptoms:
- Claude doesn't recognize agent team commands
- "Agent teams not enabled" message
- Can't spawn teammates
Solutions:
Check setting is saved:
bashcat ~/.claude/settings.json | grep CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMSAdd to settings.json if missing:
json{ "env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" } }Restart Claude Code:
bashpkill -f "claude" claudeVerify: Try creating team:
Create an agent team
If still not working:
- Check JSON syntax (no trailing commas)
- Verify file is at
~/.claude/settings.json - Try environment variable instead:bash
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 claude
See SOP-001: Enable Agent Teams
Teammates Not Appearing
Problem: Teammates don't show up after creation request
Symptoms:
- Ask for team, nothing happens
- No teammates visible in Shift+Down cycling
- Task list empty
Diagnosis:
Task might be too simple:
Claude analyzes whether task needs parallelization If simple enough for 1 agent, Claude won't create teamCheck in background:
In in-process mode, teammates might be running Try Shift+Down multiple times to cycleVerify team creation:
Check ~/.claude/teams/ directory Should contain team folder
Solutions:
Make request more explicit:
Create an agent team with 3 teammates to [task]Describe team structure:
Create an agent team: - One teammate for X - One teammate for Y - One teammate for ZGive more context:
This is a complex project. Create an agent team with 4 teammates to handle [detailed task description with requirements]Check if already running:
- In-process: Shift+Down cycles through all
- Split panes: Each has its own pane
- If truly nothing, try creating again
Last resort:
bash
# Kill any stuck Claude processes
pkill -f "claude"
# Start fresh
claudeSee SOP-002: Create Your First Team
Permission Errors
Problem: "Permission denied" during team operations
Symptoms:
- Errors spawning teammates
- Can't execute commands
- Can't write files
Common Causes:
- Permissions not pre-approved
- File system permissions issue
- Tool access restricted
Solutions:
Option 1: Pre-approve operations
Edit ~/.claude/settings.json:
json
{
"mode": "bypassPermissions"
}Restart Claude Code.
Option 2: Skip all permissions for session
bash
claude --dangerously-skip-permissionsOption 3: Approve each permission
Claude will prompt for each operation. Click "Approve" when asked.
Option 4: Adjust team permissions
After spawning teammates, adjust individual permissions:
Change [teammate] to bypassPermissions modeDisplay Mode Issues
Problem: Display mode not working as expected
Symptoms (In-Process Mode):
- Shift+Up/Down not cycling through teammates
- Ctrl+T not showing task list
- Can't enter teammate session
Solutions:
Verify in-process mode:
bashclaude --teammate-mode in-processCheck terminal supports shortcuts:
- Some terminals override Shift+Up/Down
- Try different terminal if not working
- macOS Terminal, iTerm2, VSCode, Windows Terminal all usually work
Try typing instead:
Show me the task list Tell me the current status What's the next teammate?
Symptoms (Split Panes Mode):
- "tmux not found" error
- Panes not appearing
- Click not working
Solutions:
Install tmux:
bash# macOS brew install tmux # Ubuntu/Debian sudo apt-get install tmux # Fedora sudo dnf install tmux # Verify tmux --versionInstall it2 for iTerm2:
bashpip install it2Then enable Python API:
- Open iTerm2 → Settings → General
- Check "Enable Python API"
- Restart iTerm2
Switch back to in-process:
bashclaude --teammate-mode in-processTry auto mode:
json{ "teammateMode": "auto" }
See SOP-003: Configure Display Modes
Message Delivery Issues
Problem: Messages not reaching teammates
Symptoms:
- Tell teammate to do something, they don't respond
- Broadcast doesn't reach everyone
- Messages disappear
Solutions:
Verify teammate is active:
Shift+Down (in-process mode) Can you see the teammate?Check if teammate is stuck:
- They may be in middle of long task
- Give them time to finish
- Or ask them to stop:
Tell [teammate] to pauseSend message again:
Tell [teammate]: [message]Try direct interaction:
- In-process: Shift+Down + Enter
- Type message directly
- Escape to return
Respawn if unreachable:
The teammate seems stuck. Shut down [teammate] Spawn replacement teammate for [task]
File and Permissions Issues
Problem: Teammates can't edit files or run commands
Symptoms:
- "Cannot edit file" errors
- "Cannot execute command" errors
- Teammates stuck
Solutions:
Check delegate mode:
- If delegate mode enabled, lead can't edit
- Switch:
Shift+Tabto toggle - Or tell lead:
Exit delegate mode
Pre-approve permissions:
json{ "mode": "bypassPermissions" }Use skip flag:
bashclaude --dangerously-skip-permissionsChange individual teammate:
Set [teammate] to bypassPermissions modeCheck file ownership:
bash# See if Claude can access files ls -la [file] # May need to adjust permissions chmod 644 [file]
Task List Issues
Problem: Tasks not showing or not updating
Symptoms:
- Ctrl+T doesn't show tasks
- Tasks show wrong status
- Can't assign tasks
- Tasks stuck on "pending"
Solutions:
Verify in lead session:
- Task list only visible to lead
- Make sure you're in lead's session
- Try Shift+Down back to lead
Refresh view:
Show me the task listCheck task file manually:
bashls ~/.claude/tasks/[team-name]/ cat ~/.claude/tasks/[team-name]/task-1.jsonTasks stuck on pending:
Why isn't this task being claimed? Assign task #3 to [teammate]Manual status update (if stuck):
Manually mark task #5 as complete
Team Cleanup Issues
Problem: Can't clean up team
Symptoms:
- Cleanup command hangs
- "Teammates still running" error
- Team folder remains after cleanup
- Orphaned processes
Solutions:
Shut down all teammates first:
Ask all teammates to shut downWait for graceful shutdown:
- Give them 10-15 seconds
- They may need to finish current task
Force shutdown if needed:
Force shutdown all teammatesThen clean up:
Clean up the teamManual cleanup if stuck:
bash# Remove team directory rm -rf ~/.claude/teams/[team-name] # Remove tasks rm -rf ~/.claude/tasks/[team-name] # Kill orphaned tmux session (if split panes) tmux ls tmux kill-session -t [session-name]Kill stuck Claude process:
bashpkill -9 -f "claude"
Performance Issues
Problem: Team running slowly
Symptoms:
- Commands taking long time
- Teammates slow to respond
- Messages delayed
- High CPU/memory usage
Solutions:
Reduce team size:
- Fewer teammates = faster
- Try 2-3 instead of 5
Use faster model:
Create team with Haiku teammatesSplit complex work:
- Multiple teams in sequence
- Better than one large team
Check system resources:
bash# macOS/Linux top # Windows tasklistClose other apps:
- Free up RAM
- Reduce CPU contention
Reduce task scope:
- Fewer teammates working
- on smaller subsets
Lead Doing Work Instead of Delegating
Problem: Lead implements instead of coordinating
Symptoms:
- Lead editing code instead of delegating
- Teammates idle while lead works
- Lead becomes bottleneck
Solutions:
Tell lead explicitly:
Wait for your teammates to complete their tasks before proceedingEnable delegate mode:
Press Shift+TabAssign work more specifically:
Assign task #3 to [teammate] Don't implement it yourself - let them do itFocus lead on synthesis:
Stop working on code. Coordinate your teammates instead. Check on each one's progress.
Keyboard Shortcuts Not Working
Problem: Shortcuts don't respond
Symptoms:
- Shift+Up/Down doesn't cycle
- Ctrl+T doesn't show tasks
- Shift+Tab doesn't toggle delegate
- Enter doesn't enter teammate session
Diagnosis:
Terminal may intercept shortcuts:
- Some terminals use these for own functions
- VS Code terminal is common conflict
- Try different terminal
You may not be in right mode:
- Some shortcuts only work in certain modes
- Shift+Up/Down only in-process mode
- Ctrl+T only in lead session
Timing issue:
- Give Claude time to process
- Double-check you're in right session
Solutions:
Try different terminal:
- macOS: Native Terminal, iTerm2
- Linux: GNOME Terminal, Konsole
- Windows: Windows Terminal, PowerShell
Use commands instead:
Show me the task list (instead of Ctrl+T) What teammates are active? (instead of Shift+Down)Verify mode:
In-process mode: Shift+Up/Down, Ctrl+T, Enter, Escape work Split panes mode: Click panes, use tmux shortcuts Delegate mode: Shift+Tab to toggle
Stuck Teammates
Problem: Teammate not responding or stuck
Symptoms:
- Teammate not responding to messages
- Appears hung or stuck
- Won't move to next task
- Long time without progress
Solutions:
Try to communicate:
Tell [teammate]: Are you still working?Give them time:
- Some tasks take longer
- Wait a few minutes for response
Enter their session:
Shift+Down to find them Enter to see what they're doing Escape to go backGive new instruction:
Tell [teammate]: Let's try a different approachForce interrupt:
Escape key while in their session Stops current action/turnShutdown and replace:
Shut down [teammate] Spawn new teammate for same taskCheck error state:
[In teammate's session, look for error messages]
Data Consistency Issues
Problem: Inconsistent team state
Symptoms:
- Task shows "completed" but work isn't done
- Task dependencies don't resolve
- Teammate states don't match
- File conflicts between teammates
Solutions:
Check task manually:
bashcat ~/.claude/tasks/[team]/task-N.jsonRevert if incorrect:
Reopen task #5 (it wasn't actually complete)Avoid file conflicts:
- Assign different files to different teammates
- Don't have 2 teammates edit same file
Set clear task boundaries:
- Each teammate owns distinct work
- Clear interfaces between modules
Manual resync if needed:
bashrm -rf ~/.claude/tasks/[team] rm -rf ~/.claude/teams/[team] # Rebuild team
Contact & Further Help
If you encounter issues not covered here:
Check relevant SOP:
Review workflow guide:
Check architecture:
Ask the chat widget:
- Use "Ask the Docs" widget (bottom right)
- Describe your issue
- Get instant help