Documentation menu

CLI

The current hostwright command surface and the planned first-release commands.

The hostwright command line is the primary way you interact with the control plane. This page separates commands implemented today from commands planned for the first supported release.

CLI lifecycle from init, validate, plan, doctor to the planned apply, status, and down commands. — Solid commands are implemented today; dashed commands are planned.

Commands

Command	Status	Mutating?	Purpose
`hostwright --version`	implemented	read-only	Print the current development version.
`hostwright init`	implemented	writes files	Create `hostwright.yaml` only when absent.
`hostwright validate`	implemented	read-only	Check the restricted manifest subset and semantic rules.
`hostwright doctor`	implemented	read-only	Run safe local checks without calling Apple container commands.
`hostwright plan`	implemented	read-only	Show a non-mutating manifest-level plan and state that runtime observation is unavailable.
`hostwright status`	implemented	read-only	Show manifest-level status only.
`hostwright apply`	planned	mutating	Validate, compute a plan, persist intent, and apply idempotently.
`hostwright logs`	planned	read-only	Fetch or stream service logs, honest about runtime limits.
`hostwright restart`	planned	mutating	Restart a service or project per policy and record an event.
`hostwright down`	planned	mutating	Stop project resources per ownership rules; preserves named volumes by default.
`hostwright clean`	planned	mutating	Remove stale, owned resources. Dry-run first.

Read-only first

The implemented commands you reach for while iterating — validate, plan, doctor, and status — never change runtime state. You can run them freely.

Destructive commands

down and clean are planned commands. They can remove resources, so the first release requires safe behavior:

hostwright down --dry-run        # preview what would stop
hostwright clean --dry-run       # preview stale, owned resources
hostwright clean --confirmed     # remove safe, stale, owned resources only
hostwright clean --volumes       # requires explicit confirmation; lists every named volume

Cleanup is not implemented today. The release requirement is that cleanup only touches resources Hostwright can prove it owns. See the safety model.

hostwright.yaml reference
Reconciliation — what current plan does and what future apply must do.
Limitations