Allow passing --channels to spawned team agents

Feature Request

Is your feature request related to a problem?

When using the team system (Agent tool / TeamCreate), spawned teammate agents cannot be given their own communication channel connections (e.g., Discord via --channels plugin:discord@claude-plugins-official).

Currently, the team lead can communicate with external channels (Discord, Telegram, etc.), but teammates are isolated to tmux panes. The only way to interact with teammates from Discord is to relay messages through the team lead, which adds friction.

Describe the solution you'd like

Allow passing --channels (or equivalent channel configuration) to agents spawned via the team system. Ideally:

1. When spawning a team agent, support a channels parameter (e.g., in the Agent tool or TeamCreate)
2. Each spawned agent gets its own channel connection — for Discord, this could auto-create a dedicated channel (e.g., #mlip-trainer) that maps to that agent
3. The agent can then receive instructions and send responses directly through its own Discord channel

This would enable managing a full team of agents from Discord (or Slack/Telegram) without needing to switch to tmux panes.

Describe alternatives you've considered

• Relay through team lead: Works but adds latency and loses the direct conversation context
• Manual tmux launch with --channels: Gives agents Discord access but they lose the team system (SendMessage, shared tasks, coordination)
• MCP server per agent: Subagents support mcpServers in agent definition files, but team agents don't

Additional context

Use case: A research group coordinator (team-lead) manages multiple specialized agents (mlip-trainer, dmft-expert, etc.) from Discord on mobile. Being able to talk to each agent in its own Discord channel would make the team system much more practical for remote/async workflows.

🤖 Generated with Claude Code