Install
The RunWisp daemon ships as a single static Go binary. There is nothing to compile, no language runtime to install, and no database to provision. Pick whichever delivery method fits your workflow.
Install
Section titled “Install”The installer fetches the right binary for your platform, verifies
its checksum, and puts runwisp on your PATH.
curl -fsSL https://get.runwisp.com | shIf you already have Bun or Node, you can launch the prebuilt binary without a global install. The npm package is a thin shim that downloads the matching native binary — RunWisp itself is not a Node application.
bunx runwispnpx runwispThis is also the recommended path for CI runners and ephemeral environments where you do not want to keep a binary on disk.
Another option is installing it globally as a binary:
bun add -g runwispnpm install -g runwispGrab a tarball from the GitHub releases
page. Assets are
named runwisp-{linux,darwin}-{x64,arm64}.tar.gz, with a matching
checksums-sha256.txt published alongside them. Verify the
checksum, then move the binary somewhere on your PATH.
tar -xzf runwisp-linux-x64.tar.gzsudo mv runwisp /usr/local/bin/runwispBuilding requires Go 1.25+ and Bun. Clone the repo, install dependencies, and run the workspace build.
git clone https://github.com/runwisp/runwispcd runwispbun installbun run buildThe compiled binary lands at apps/runwisp/runwisp.
Verify the install
Section titled “Verify the install”runwisp --version # or: bunx runwisp --versionYou should see the release version. If you get “command not found”,
make sure your installer’s target directory is on PATH and reopen
your shell.
Next step
Section titled “Next step”Continue to Your first task to write a
runwisp.toml, start the daemon, and watch a run stream live.