The production control plane is a native Swift service. Its implementation lives in Sources/ModelMatrixControllerCore/; the executable entrypoint is Sources/ModelMatrixController/.
start-model-mac.shlaunches profile-backed model servers.stop-all-models.shsafely stops tracked model processes.model-profiles/contains user profiles and examples.swiftbar/local-models.15s.shexposes the same controller through SwiftBar.
The Swift controller owns profile parsing, status and health probes, lifecycle serialization, authentication, doctor diagnostics, Factory Droid sync, benchmark orchestration, status caching, and the /api/* HTTP service.
Build once:
swift build -c release --product ModelMatrixControllerRun against this controller root:
CONTROLLER="$(swift build -c release --show-bin-path)/ModelMatrixController"
$CONTROLLER triage --root Controller
$CONTROLLER capabilities --root Controller
$CONTROLLER status --root Controller
$CONTROLLER start <profile> --root Controller
$CONTROLLER stop <profile> --root Controller
$CONTROLLER restart <profile> --root Controller
$CONTROLLER switch <profile> --root Controller
$CONTROLLER stop-all --root Controller
$CONTROLLER doctor --root Controller
$CONTROLLER doctor health --root Controller
$CONTROLLER doctor --fix --dry-run --root Controller
$CONTROLLER benchmark --suite quick --root Controller
$CONTROLLER serve --root ControllerDistributed app builds embed the signed controller binary, runtime assets, and LaunchAgent property list. The app registers the agent with SMAppService and seeds runtime assets under:
~/Library/Application Support/ModelMatrix/Controller
Source checkouts can install the same native service directly:
./Controller/install-modelmatrix-controller.shNo Python runtime is required by the controller or its tests.
swift test --filter ModelMatrixControllerTestsCoverage includes profile parsing, endpoint conflicts, lifecycle actions, authentication, request validation, status and doctor contracts, integrations, benchmarks, and a real loopback HTTP listener.