Official Addons
| 언어: 🇺🇸 English | 🇰🇷 한국어 |
Addons extend a Ghost-ALICE OS install with optional capability packages on top of the core skills. This page is the contributor and operator reference for the addon sources surfaced on the homepage: official aliases, custom repositories, tenant packages, and local development addons. They all enter through the same installer entrypoint.
For the full install command surface, read installation. For how to package an addon you build or bring in, read the addon authoring guide.
Contents
Official Addons
Official addons are maintained alongside the Ghost-ALICE core and are installed from the core checkout with a short alias. You pass the alias to the Core installer; the installer resolves it to the maintained source and reads that package’s addon manifest.
Install an official addon by passing its alias to the installer:
bash install.sh --addon autopilot
| Addon | Purpose | Install | Details |
|---|---|---|---|
| autopilot | Return eligible tasks from the model’s explicitly approved plan through the registered Stop adapter. | bash install.sh --addon autopilot |
AidALL/ghost-alice-autopilot |
Core 0.5.1 and Ghost-ALICE Autopilot 0.5.1 use the routing and managed completion APIs. Ghost-ALICE Autopilot requires Core 0.5.1 or later. Source checks, native runtime validation and publication establish separate evidence.
The responding model judges work and meaning; Core authenticates the review records. Ghost-ALICE Autopilot consumes that result and selects eligible work from the model’s admitted plan. See the Core architecture for the standalone flow and the Autopilot architecture for addon hooks and conditional host delivery.
Custom, Tenant, And Local Development Addons
When an addon is not an official alias, install it from an explicit path or URL with --addon-source. The source can be a local directory, a fork, a tenant-specific package, or a checkout you are developing.
bash install.sh --addon-source /path/to/addon-repo
--addon-source also accepts a repository URL:
bash install.sh --addon-source https://github.com/your-org/your-addon.git
- Custom repositories: install an addon you maintain or fork by pointing
--addon-sourceat its repository URL. The installer reads the addon manifest from that source instead of an official alias. - Tenant packages: the tenant operator selects a bundle authorized for that organization or customer and passes its location through
--addon-source. The installer reads that source’s addon manifest; choosing a source does not itself grant entitlement. - Local development addons: while authoring an addon, point
--addon-sourceat the working checkout on disk (for example/path/to/addon-repo) to install and re-test it without publishing first.
Where To Go Next
- Installation: core install, official addons, custom addon sources, status, doctor, update, and platform selection.
- Addon authoring guide: manifest format and packaging guidance for addons you build or bring in.