Skip to content

halo onboard install

Render a ring’s managed config for this OS and show exactly what lands where; –apply writes it

Managed config lives in admin-owned paths (e.g. /Library/Application Support/ClaudeCode on macOS, /etc on Linux), so –apply usually needs sudo; –root DIR stages the same tree under DIR. A file that differs is backed up once to <file>.halos-backup. A file Halos did not write (one your MDM pushed, say) is reported as foreign and –apply refuses to touch anything unless –replace-existing is set. Idempotent: a second –apply writes nothing.

Terminal window
halo onboard install [flags]
Flag Shorthand Type Default Description
--apply bool false write the files (default: dry run)
--policy-dir string policy repo directory (default “.”)
--replace-existing bool false also replace files Halos did not write (originals kept at <file>.halos-backup)
--ring string ring to install (default: the GA ring)
--root string write under this directory instead of the real paths
--show bool false include each file’s contents
Flag Shorthand Type Default Description
--output string text output format: text|json

halo onboard