`hiveloom apply`

Reads a manifest file and reconciles the tenant’s agent set against it. Use this to manage agents in source control or to recreate a tenant’s state on a fresh instance.

Synopsis


hiveloom apply --file <FILE> [OPTIONS]

Options

Flag	Default	Description
`-f, --file <FILE>`	— (required)	Path to the manifest. YAML or JSON.
`--tenant <TENANT>`	`default`	Target tenant.
`--endpoint <URL>`	—	API endpoint.
`--token <TOKEN>`	—	Bearer token.
`--prune`	off	Delete agents present in the tenant but absent from the manifest.
`--json`	—	JSON-formatted result.

Manifest shape

The manifest lists the desired agents:


agents:
  - name: pirate
    model: anthropic:claude-sonnet-4-6
    credential: anthropic-default
    system: |
      Reply only in pirate-speak.
    capabilities:
      - file: ./skills/pirate-voice.md
  - name: reviewer
    model: anthropic:claude-sonnet-4-6
    credential: anthropic-default
    system: |
      Code reviewer focussed on diff hygiene.

Generate one from an existing agent with hiveloom agent export.

Examples

Apply without pruning (safe default):


hiveloom apply --file ./agents.yaml --tenant acme

Reconcile destructively (deletes anything not in the manifest):


hiveloom apply --file ./agents.yaml --tenant acme --prune

Capture the result for CI:


hiveloom apply --file ./agents.yaml --json | tee apply-result.json

What changes

New agents are created at version 1.
Existing agents whose definition differs get a new version.
Without --prune, agents not in the manifest are left untouched. With --prune, they are deleted.
Capability files are read at apply time and inlined into the agent’s capability bindings.