Installation

macOS Studio

On Apple Silicon Macs, install JacqOS Studio from the current DMG:

Preview DMG · jacqos-studio-macos-preview.dmg · 88.4 MB

Download the current macOS DMG from the website Download button or from studio_macos.url in the release channel metadata.
Open the DMG.
Drag JacqOS Studio.app to /Applications.
Open JacqOS Studio.app.

The DMG contains the native SwiftUI Studio app, the bundled jacqos engine, the optional jacqos CLI shim, app resources, entitlements, and release manifest/checksum sidecars. You do not need Rust, Cargo, Homebrew, Node.js, GPUI, or the legacy Rust/Iced Studio app.

Preview DMGs are signed with a Developer ID and notarized by Apple, so they open like any other Mac app.

The current public DMG names are:

Channel	DMG asset
Stable	`jacqos-studio-macos.dmg`
Preview	`jacqos-studio-macos-preview.dmg`

Use the release channel metadata rather than hard-coding a versioned URL:

https://download.getjacqos.com/channels/stable.json
https://download.getjacqos.com/channels/preview.json

The studio_macos entry gives the DMG URL, manifest URL, checksum URL, SHA-256 hash, and size for the current channel.

Optional macOS CLI

The macOS app can install a small CLI shim from inside Studio:

Open JacqOS Studio.app.
Open the app menu and choose Install CLI.
Run jacqos --version in a new terminal.

The shim is intentionally tied to the installed SwiftUI app. jacqos studio opens JacqOS Studio.app; other commands run the bundled jacqos engine from inside that app bundle. If you move or rename the app after installing the shim, open the app from its new location and choose Repair CLI. Choose Uninstall CLI to remove the shim.

You can also install the standalone macOS CLI bundle from the release channel metadata. That path is useful for automation and shell-only machines, but the DMG is the primary macOS Studio install path.

Linux CLI

Install the latest Linux bundle with:

curl -fsSL https://www.jacqos.io/install.sh | sh

This detects your platform, downloads the correct bundle from https://download.getjacqos.com, verifies the checksum, installs to ~/.local/bin, and seeds bundled workspaces under ~/JacqOS/workspaces/examples/.

The installer falls back from stable to the latest installable preview bundle when a stable bundle is not published for your platform yet.

Pin a specific version:

JACQOS_VERSION=0.4.7-preview curl -fsSL https://www.jacqos.io/install.sh | sh

Custom install directory:

JACQOS_INSTALL_DIR=/opt/jacqos/bin curl -fsSL https://www.jacqos.io/install.sh | sh

Windows Preview CLI

Windows currently ships as a preview CLI bundle:

iwr https://www.jacqos.io/install.ps1 -UseBasicParsing | iex

Or download jacqos-windows-x86_64-preview.zip from the release metadata, extract it, and run install.ps1.

Manual Bundle Download

If you prefer to download a CLI bundle manually, use the release channel metadata to find the current version and checksum.

Platform	Asset	Status	Install path
Linux x86_64	`jacqos-linux-x86_64.tar.gz` or `jacqos-linux-x86_64-preview.tar.gz`	GA or preview	Extract and run `./install.sh`
Linux arm64	`jacqos-linux-arm64.tar.gz` or `jacqos-linux-arm64-preview.tar.gz`	GA or preview	Extract and run `./install.sh`
macOS arm64 CLI	`jacqos-macos-arm64.zip` or `jacqos-macos-arm64-preview.zip`	Optional CLI bundle	Extract and run `./install.sh`
Windows x86_64	`jacqos-windows-x86_64-preview.zip`	Preview	Extract and run `install.ps1`
macOS x86_64	not published	Not shipped in V1	Use Apple Silicon or the contributor path

Bundled Workspaces

Release bundles seed the current demos under ~/JacqOS/workspaces/examples/:

Car Dealership Chat (Live) — a live, OpenAI-backed dealership agent. It proposes offers to customers; an ontology rule blocks any proposal below the pricing floor before it can be sent. Requires OPENAI_API_KEY (see below).
Drive-Thru Ordering — a fallible-sensor demo where absurd parsed orders stay staged and never reach the POS. No API key needed.

If a bundled workspace destination already exists, the installer leaves it in place instead of overwriting user-owned changes.

OpenAI Key For Live Demos

The Car Dealership Chat (Live) workspace calls a real model, so it needs an OPENAI_API_KEY. Export it in your shell and launch Studio from there so the app inherits it:

export OPENAI_API_KEY=sk-...
jacqos studio

Studio warns when OPENAI_API_KEY is missing on a live workspace. Without the key the workspace still opens and its declared facts load, but the live chat turn cannot call the model. Deterministic demos such as Drive-Thru Ordering need no key.

Verify

Check the CLI:

jacqos --version

On macOS, open JacqOS Studio.app from /Applications. If you installed the CLI shim from the app, this also works:

jacqos studio

On Linux or shell-only macOS installs, run:

jacqos studio

Studio opens to the workspace picker. Choose Car Dealership Chat (Live) (set OPENAI_API_KEY first) or Drive-Thru Ordering, then run the demo.

Updating

Update a CLI bundle in place with:

jacqos self-update

To check for updates without installing:

jacqos self-update --check

For the macOS app, download the latest DMG from the website or release channel metadata, then replace the app in /Applications. If you installed the CLI shim, open the updated app and choose Repair CLI.

What You Get

SwiftUI Studio app on macOS — provenance, facts, effects, demos, local examples, and cloud sign-in from a native app.
Optional CLI shim on macOS — jacqos studio opens the app; other commands run the bundled engine.
CLI bundles for Linux, Windows preview, and shell-only macOS workflows.
Scaffold — generate new app directories.
Dev shell — watch files and hot-reload ontology and mappers.
Replay and verify — deterministic replay plus invariant and fixture checks.
Cloud commands — sign in, select a scope, publish, issue scoped runtime tokens, send observations, and replay hosted evidence.
Export — freeze evaluation packages, hosted evidence, and observation logs.

System Requirements

macOS 13+ on Apple Silicon for the Studio DMG.
Linux x86_64 or Linux arm64 for CLI bundles.
Windows x86_64 for the preview CLI bundle.
No runtime dependencies.

Contributor Path

If you are developing inside the JacqOS source repository, cargo install --path tools/jacqos-cli remains available as the contributor-only path. End users should install the macOS DMG or release bundle above.