Spawn Instance

To fork and configure a new autonomous agent repository instance, you pass a variable in the form name: purpose. The system handles pre-flight checks, generates a dynamic skill plan, and writes configuration files like aeon.yml to set up the child repo.

Fleet management for autonomous agent instances is the process of registering newly forked repositories to a parent memory. This enables centralized monitoring and coordination of deployed agents across the entire network.

To set up GitHub Actions for a newly forked AI agent repository, the deployment process includes automated post-flight checks that enable Actions. This ensures the autonomous workflows are triggered immediately after configuration.

Yes, you can dynamically generate a skill plan from a live catalog when deploying an AI agent. The system builds the inventory without hardcoded lists, validates the inputs, and writes per-instance configurations for the specific purpose.

Required configuration files to deploy a new AI agent instance include aeon.yml, SETUP.md, and CLAUDE.md. The automated setup writes these files and performs a memory reset to ensure the child repository starts with a clean slate.

Spawning a new repository instance does not require manual memory reset. The automated setup process handles the memory reset automatically, validating inputs and registering the new instance in the parent fleet for monitoring.