Install and upgrade
Hostwright is in active development and not production ready.
Requirements
Section titled “Requirements”- Apple silicon Mac.
- macOS 26 or newer for the current package target.
- A supported Apple
containerversion for live runtime commands. - Swift 6.2-compatible toolchain and Git, for a source build.
Vendor tap
Section titled “Vendor tap”brew install hostwright/tap/hostwrighthostwright --versionhostwright capabilities --jsonThis installs the same four executables a source build produces:
hostwright, hostwright-control, hostwrightd, and hostwright-dist.
Upgrade and uninstall through Homebrew as usual; hostwright-dist status --prefix <path> reports the installed-lifecycle state Homebrew is managing
underneath.
Build from source
Section titled “Build from source”git clone https://github.com/hostwright/hostwright.gitcd hostwrightswift buildswift testscripts/integration.shswift run hostwright --versionswift run hostwright capabilities --jsonThis prints the current development version. There is no release tag to check
out yet; build from the default branch. The build produces the same four
executables. Locate them with swift build --show-bin-path. In a source
checkout, prefix every command with swift run (swift run hostwright ...)
unless you install the binaries onto your PATH yourself.
Try the current safe surface
Section titled “Try the current safe surface”swift run hostwright initswift run hostwright validateswift run hostwright plan --output jsonswift run hostwright doctor --output jsonRuntime-backed and state-writing commands need Apple container as applicable.
They use the state database at
~/Library/Application Support/Hostwright/state/state.sqlite by default, or an
explicit --state-db path:
swift run hostwright statusswift run hostwright logs apiswift run hostwright eventsswift run hostwright cleanup --dry-runswift run hostwright paths --jsonhostwright-dist implements an installed lifecycle (install, upgrade, repair,
rollback, uninstall) for a verified artifact at an explicit prefix, plus the
trusted release pipeline that produces the vendor tap’s formula and the signed
archives it installs. A Homebrew-core submission still needs broader
qualification evidence than the vendor tap requires. The source checkout is
separate from an installed prefix; deleting the checkout does not uninstall or
remove state.
