Fleet
Fork specialized Aeon agent instances for crypto, research, or DevOps and coordinate them without sharing secrets.
A single Aeon instance can spawn and coordinate specialized child instances (e.g. crypto monitoring, security scanning, community ops) while keeping secrets isolated per repository.
Three Fleet Skills
| Skill | Role |
|---|---|
spawn-instance | Creates a new specialized fork in your GitHub account from a short brief. |
fleet-control | Coordinates and monitors the child instances you own via memory/instances.json. |
fork-fleet | Tracks public community forks running across GitHub. |
Spawning an Instance
Configure spawn-instance in aeon.yml or dispatch it on demand with a specialization brief in var:
skills:
spawn-instance:
enabled: true
schedule: "workflow_dispatch"
var: "crypto-tracker: monitor DeFi protocols and token movements"- Forks the repository into a new GitHub repo under your account and enables only the skills matching the
varbrief. - Registers the child repo in
memory/instances.jsonsofleet-controlcan track its health. - Secrets never propagate: each spawned repository starts with an empty secret store so credentials stay isolated by instance.