colony-spawning

Spawn isolated Colony CLI subprocesses for independent sessions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Aevonix/colony-ai --skill colony-spawning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: colony-spawning
Source: https://github.com/Aevonix/colony-ai/tree/main/skills/autonomous-ai-agents/colony-agent
Command: npx skills add https://github.com/Aevonix/colony-ai --skill colony-spawning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn fully isolated Colony subprocesses to run independent CLI sessions, enabling separated contexts for long-running tasks and multi-agent collaboration without shared state.

Core Features & Use Cases

  • Independent Colony processes with their own sessions, tools, and terminal environments
  • Support for one-shot non-interactive mode (-q) and interactive PTY sessions
  • Parallelization and orchestration of multiple agents or tasks

Quick Start

Start an autonomous Colony subprocess by running colony in the CLI with PTY mode and submit your task to begin the session.

Frequently Asked Questions about colony-spawning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I spawn autonomous subprocesses for long-running CLI tasks?

You can spawn autonomous subprocesses for long-running CLI tasks by initializing fully isolated Colony sessions that operate with independent contexts, separate tools, and distinct terminal environments without sharing state.

Can I run parallel agents in interactive PTY sessions?

Yes, you can run parallel agents in interactive PTY sessions. The system supports multi-turn collaboration across autonomous processes, allowing simultaneous interactive terminal environments for complex orchestration.

What is the best way to execute one-shot non-interactive tasks in an isolated context?

The best way to execute one-shot non-interactive tasks is by using the -q mode flag. This initiates a fully isolated Colony subprocess to run a single automated task without requiring an active interactive terminal session.

Do I need the Colony CLI installed to spawn independent subprocesses?

Yes, spawning independent subprocesses requires the Colony CLI installed on your system PATH. You also need an API key configured at ~/.colony/.env to authenticate and manage the isolated sessions.

Why use isolated subprocesses for multi-agent collaboration?

Isolated subprocesses provide separated contexts for multi-agent collaboration, preventing shared state conflicts. Each autonomous process maintains its own session and terminal environment, ensuring reliable parallelization.

Does spawning separate CLI sessions support parallelization and task orchestration?

Spawning separate CLI sessions directly supports parallelization and task orchestration. It enables multiple autonomous agents or long-running tasks to execute simultaneously in fully independent environments.