DOCUMENTATION / Start

Install

One command on macOS and Linux. Or run it from source.

Install script

curl -fsSL https://manyeya.github.io/modisa/install.sh | sh

It downloads the release for your platform, checks it against the published SHA-256, and puts modisa in ~/.local/bin. Releases exist for macOS on Apple silicon and Linux on x64 and arm64 (glibc).

Variable	Effect
`MODISA_INSTALL_DIR`	Where the binary goes (default `~/.local/bin`).
`MODISA_CHANNEL=staging`	Install the latest prerelease instead of the latest release.

With a package manager

A package manager installs modisa, updates it, and removes it again.

With	Install	Remove
mise	`mise use -g github:manyeya/modisa`	`mise uninstall github:manyeya/modisa`
Debian, Ubuntu	`sudo apt install ./modisa_<version>_<arch>.deb`	`sudo apt remove modisa`
Fedora, RHEL	`sudo dnf install ./modisa-<version>-1.<arch>.rpm`	`sudo dnf remove modisa`

The .deb and .rpm files are attached to every release. When one of these tools installed modisa, modisa update tells you its update command rather than replacing the binary itself.

From a release

Every release on GitHub Releases carries one binary per platform, the .deb and .rpm packages, a SHA256SUMS file, and the manifest.json that the installer and modisa update read. Download the binary for your platform, chmod +x it, and put it on your PATH.

Verify a download

Every file in a release has signed build provenance: proof that the repository's release workflow built it from a tagged commit. With the GitHub CLI:

gh attestation verify modisa-darwin-arm64 -R manyeya/modisa

mise checks this automatically when it installs modisa.

From source

Needs Bun 1.3.5 or newer (for its built-in PTY). This is also the way to run modisa on an Intel Mac.

git clone https://github.com/manyeya/modisa
cd modisa
bun install
bun start

Check it

modisa --version

Then run modisa to open your first session.

Uninstall

modisa uninstall
# or, through the install script
curl -fsSL https://manyeya.github.io/modisa/install.sh | sh -s -- --uninstall

It lists what it will do and asks first. Then it removes modisa's hooks and skill from every agent, stops running sessions, and deletes saved state in ~/.local/state/modisa. Your config in ~/.config/modisa stays unless you add --purge; --yes skips the question.

If the install script put the binary there, uninstall deletes it too. If mise or a package did, finish with that tool's remove command, which modisa prints. Run it from a terminal outside modisa, since it stops every session.