Subagents Swarm Overview
How Bhai, Planner, and Executor divide complex tasks inside BhaiCode.
Complex software work needs different skills: architecture, fast implementation, careful refactoring, and review. BhaiCode coordinates those roles as a Subagents Swarm — one conversation on your side, specialist agents behind it.
Swarm structure
| Agent | Role | Focus |
|---|---|---|
| Bhai | Lead orchestrator and builder | Full-stack coding, pair programming, tool calls, debugging |
| Planner | System architect | Requirements breakdown, data modelling, ordered roadmaps |
| Executor | Heavy refactorer | Multi-file surgery, framework migrations, test generation |
| Explorer | Codebase scout | Read-only symbol tracing, dependency mapping, file discovery |
| Auditor | Security auditor | Vulnerability scanning, secret leaks, performance bottlenecks |
| Reviewer | Code reviewer | Lint compliance, import hygiene, code cleanliness |
How a task moves through the swarm
You talk to Bhai
You describe the goal in English or any supported Indian language. Bhai reads the workspace and estimates scope.
Bhai plans or hands off
Multi-phase or architectural work goes to Planner. Deep refactors and migrations go to Executor. Explorers and auditors run alongside when the task needs them.
Subagents report back
Results return to Bhai, which presents the consolidated change in the diff viewer for your review.
Delegation is automatic — you never address a subagent directly. If you want a specific approach, say so in your prompt to Bhai.