The rust-preview distribution is an independent, experimental preview. It is not an official Apache Software Foundation release and is not approved, endorsed or supported by the ASF.
npm install --global @maka-agent/cli@rust-preview
The launcher selects the matching native executable and forwards arguments, standard I/O and exit status. Exact-version optional dependencies carry the CLI, which includes maka terminal-shell, and the desktop shell with its authored app. On macOS the desktop shell and app are inside Maka.app; other platforms carry maka-desktop-shell and its adjacent app/ sidecar. The preview targets macOS arm64, Linux x64 with glibc, and Windows x64. WSL uses the Linux executable with a matching Windows helper for Computer Use.
The latest tags remain empty placeholders, including the separate maka-agent package. They contain no CLI, runtime, dependencies or install scripts. The placeholder source lives in placeholder; preview artifacts must stay on rust-preview.
Run maka to open the NSH terminal workbench. It discovers or starts the Host at ~/.maka/application/host; use --root HOST_ROOT to select another Host and --session SESSION_ID to open an existing conversation. maka --help lists automation commands. See the product guide for composition and installation commands.
Launch the desktop with maka desktop --root HOST_ROOT. This required path selects the business Host: a missing Root gets the standard read-only Host, and an existing Root reopens its saved deployment. The launcher keeps its verified Host client until the shell exits; other connected clients keep the Host alive. The packaged shell reads its adjacent app independently of the working directory. See desktop-shell for direct development commands.
Launch the NSH terminal workbench with maka terminal-shell. It discovers or starts the Host at ~/.maka/application/host; use --root HOST_ROOT for another Root or --session SESSION_ID for an existing conversation. maka terminal-shell --help lists its options. See terminal-shell for source builds.
Create a source candidate from a committed revision with just source <version>. Build each native target from that same archive:
just package <source.tar.gz> <target> <build-id> native-preview
Collect all three native packages and receipts, plus the source archive and SHA-512 sidecar. Then run:
just release-prepare native-preview just release-check native-preview just publish native-preview
release-check installs and exercises the prepared artifacts offline; run it on each target platform. Publication uploads native components before the launcher and verifies the channel tags. Retry the same artifacts after interruption. Use one publisher per channel because npm tags have no conditional update operation.
The publication workflow can build and verify with publish=false. Unofficial publishing runs in M4n5ter/maka-agent on feat/runtime-host-rust, requires explicit publish=true, and uses its dedicated npm-rust-preview environment. It does not publish from the ASF repository.
See native build tooling for dependencies, V8 caching and notices, and source releases for archive verification and signing.