subagent-spawner

You can run parallel tasks by spawning independent sub-agent sessions via `sessions_spawn`, delegating long-running operations to background workers so the main agent remains responsive and unblocked.

Multi-agent orchestration involves coordinating complex pipelines where a primary agent manages several worker agents. Management functions include using `sessions_list`, `sessions_history`, `sessions_send`, and `sessions_kill` to direct and control the sub-agents.

You can communicate with or terminate background sub-agents using `sessions_send` to transmit messages and `sessions_kill` to stop the session. Additionally, `sessions_list` and `sessions_history` allow you to track active runs and review outputs.

Yes, thread-bound sessions can be created to maintain persistent, focused sub-agent interactions within Discord threads. This allows background workers to handle specific follow-up tasks without losing context or blocking the primary workflow.

No additional dependencies are required to spawn and manage sub-agents for isolated research or background scanning. The skill operates independently using built-in session management commands to handle parallel execution.

You should avoid using parallel sub-agents for lightweight or synchronous tasks where the overhead of spawning a session outweighs the benefits, reserving orchestration for time-consuming operations that require non-blocking execution.