Magistr’s command-line program connects a project to your coding agent and manages its saved work. This page installs the program. Agent setup connects it to a particular project.
The current preview is v1.0.0-beta.2, a beta pre-release for Apple Silicon macOS 15 or later. Magistr has not been officially publicly released. The beta is published on npm; it is not published to the Cargo registry. The repository is public if you prefer to build from source.
Install with npm
You need Node.js with npm. No Rust toolchain is required: the package contains the prebuilt executable. In a terminal, run:
npm install --global magistr@beta
magistr --versionThe beta tag selects the current pre-release. The last command should print
the installed version.
Build from source instead
To build the CLI yourself, you need Git, Rust 1.95 or later, CMake, and the macOS command-line build tools. Check Git, Rust, and CMake in a terminal:
git --version
rustc --version
cargo --version
cmake --versionIf the macOS build tools are missing, run xcode-select --install and finish
the system installer.
If cmake is not found, install it with Homebrew:
brew install cmakeThe Cargo build needs CMake for one dependency. Magistr reads language packs whose grammars are WebAssembly modules, and the WebAssembly runtime that loads them installs its C headers through CMake while it compiles. CMake is used only during the build; the installed program does not need it.
Install and sign in to your coding agent separately; Magistr does not provide an agent subscription.
Then choose a parent folder for the Magistr source checkout and run:
git clone https://github.com/AlrikOlson/magistr.git
cd magistr
cargo install --locked --path crates/magistr-cli
magistr --versionCargo builds the CLI and places the executable in Cargo’s binary directory,
normally ~/.cargo/bin. The source checkout is the copy of Magistr you build.
It can be separate from the project where you will use Magistr.
The last command should print the installed version. Confirm that help opens:
magistr --helpInstallation alone does not connect any project or start implementation.
If installation fails
| Symptom | What to do |
|---|---|
npm reports EBADPLATFORM |
The package supports Apple Silicon macOS 15 or later only. |
| npm reports a permissions error on global install | Use a Node.js installation managed by your user (for example through a version manager) rather than the system one, then retry. |
| Git reports that the repository is unavailable | Check your network connection and the repository URL in the clone command. |
| Rust reports an unsupported version | Install Rust 1.95 or later, then retry the locked build. |
| A compiler or linker is missing | Finish installing the macOS command-line build tools. |
failed to run custom build command for wasmtime-c-api-impl and failed to spawn cmake |
Install CMake with brew install cmake, open a new terminal, and run the install command again. |
The shell cannot find magistr |
Add npm’s global binary directory (npm prefix --global followed by /bin) or Cargo’s binary directory to your shell’s PATH, reopen the terminal, and run magistr --version. |
| An older executable still runs | Use command -v magistr to check which installation the shell selects. |
Keep the complete build error if these steps do not resolve it. A connection repair cannot fix a CLI that has not built successfully.
Next: connect your project
Continue with Connect an agent. That step creates project settings and agent connections. For the graphical application, use the separate desktop instructions.