Extensions
Install or build packaged AGH capabilities that bundle skills, agents, hooks, bridge providers, MCP servers, and subprocess services.
- Audience
- Operators running durable agent work
- Focus
- Extensions guidance shaped for scanability, day-two clarity, and operator context.
An extension is one installable unit that ships runtime capabilities behind a single manifest. The operator installs, enables, and removes the bundle as a whole; AGH wires the contained resources into the runtime registry only while the extension is enabled.
Use extensions when a capability should travel between machines or teams with one install command. If the work is only a local instruction set, a skill may be enough. If it includes multiple resources, provider-specific bridge code, or a daemon-facing Host API service, an extension gives that package a manifest, trust tier, enablement state, and operational lifecycle.
The install page is for operators who need to add, enable, disable, inspect, update, or remove an extension. The develop page is for authors who need the manifest shape, resource layout, subprocess lifecycle, and permission model before packaging an extension for a registry.
In this section
Install
Install and operate extensions
Use this page for `agh extension` install, enable, disable, update, and inspect flows, plus marketplace trust tiers.
Develop
Build extensions
Use this page for `extension.toml` manifests, bundled resources, subprocess lifecycle, and Host API permissions.