claude-team

What problem does it solve?

Prevents silent failures, misrouted messages, and session-reconnection pitfalls that break multi-agent Claude Code workflows by documenting validation steps, reconnection procedures, and coordination best practices.

Core Features & Use Cases

• Silent-failure detection: How to verify teammates and avoid SendMessage to nonexistent recipients and accidental empty teams.
• Session reconnection: Exact steps to resume orchestrator sessions by reading team config, matching leadSessionId, team and agent names, and validating TaskList.
• Coordination & cost control: Guidelines to avoid expensive broadcasts, reduce context bloat, and enforce file placement conventions for shared artifacts.
• Use Case: Reconnect a crashed orchestrator, recover task lists, and re-establish peer messaging without losing history.

Quick Start

Reconnect a crashed Claude Code team by reading ~/.claude/teams/{team-name}/config.json, copy the exact team and lead names, resume the leadSessionId with the --resume and --team-name flags, and verify TaskList shows existing tasks.