Skip to content

Configuration

Omni settings.json configures tools, dotfiles, providers, hosts, and groups. Agent resources are not stored in Omni configuration.

Agent desired/runtime state is owned by APM:

  • ~/.apm/apm.yml
  • ~/.apm/apm.lock.yaml
  • ~/.apm/marketplaces.json

Use omni agents sync and its thin APM wrappers for agent operations. There is no steady-state Omni skill store, native plugin lifecycle, or per-agent/group assignment model.

A host may keep its desired APM manifest as a template at ~/.config/omni/apm.yml, which sync copies over ~/.apm/apm.yml. It is an ordinary dotfile-managed file, not Omni configuration. omni agents migrate --host <name> previews one from a pre-APM snapshot; --write publishes wrappers and updates the migration-owned template.

Current settings schema version: 25. The top-level agents field accepts only an ignored list of host-local agent artifacts omni must leave alone; every other agents shape is rejected with instructions to use APM.

The generated JSON Schema is the authoritative field reference: spec/omni.settings.schema.json. It covers tools, dotfiles, providers, hosts, groups, ignore lists, and agent exclusions; agent packages themselves are deliberately absent.