Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Download

Most people want the desktop app: pick your platform below, download it, and open it. Every app build bundles its own jamstreamd session server, so hosting and joining need nothing else installed.

The jamstream CLI, for terminals and automation, installs in one line at the bottom of this page.

Every link on this page points at the latest release by a stable name, so a new release updates them all in place. All artifacts are listed on the releases page.

Building from source also works on every platform: clone the repository and run cargo install --path crates/cli.

macOS

Windows

Extract the app zip and run jamstream-app.exe. The zip's other file, jamstreamd.exe, is the bundled session server: keep it beside the app, or hosting on this computer stops working.

The binaries are plain zips and are not code signed. SmartScreen may show "Windows protected your PC" the first time you run the app: click More info, then Run anyway.

Right-clicking the downloaded zip, opening Properties, and ticking Unblock before extracting clears the mark for everything inside; without that, the app zip's two exes can each raise the warning once. Verifying the download confirms you have the real file.

Linux

The session server downloads are only for hosting on your own computer with the CLI alone; the desktop app bundles its own.

Architecture availability

PlatformAppCLISession server
macOSApple silicon + Intel (universal)Apple silicon + Intel (universal)bundled in app
Windowsx86_64x86_64bundled in app
Linuxx86_64x86_64x86_64 and aarch64

No arm64 builds of the app or CLI are published yet for Windows or Linux; build from source there.

Verifying a download

Every release ships a SHA256SUMS file covering every artifact:

$ curl -fsSLO https://github.com/sean-reid/jamstream/releases/latest/download/SHA256SUMS
$ sha256sum --check --ignore-missing SHA256SUMS
jamstream-cli-linux-x86_64.tar.gz: OK

On macOS that command is shasum -a 256. In PowerShell:

irm https://github.com/sean-reid/jamstream/releases/latest/download/SHA256SUMS -OutFile SHA256SUMS
(Get-FileHash jamstream-app-windows-x86_64.zip).Hash -eq (Select-String jamstream-app-windows-x86_64.zip SHA256SUMS).Line.Split(' ')[0]

True means the file matches. Get-FileHash prints uppercase and the sums file is lowercase; PowerShell's -eq ignores case, so that does not matter.

Package managers

Homebrew (macOS and Linux) and Scoop (Windows) are live, and both follow new releases, so an upgrade comes from the package manager rather than from this page. winget and the AUR are planned.

$ brew install --cask sean-reid/jamstream/jamstream   # desktop app
$ brew install sean-reid/jamstream/jamstream-cli      # CLI, with completions
scoop bucket add jamstream https://github.com/sean-reid/scoop-jamstream
scoop install jamstream-app   # desktop app, with a Start Menu shortcut
scoop install jamstream       # CLI

Install the CLI in one line

The CLI suits scripts, automation, and machines without a display; the CLI reference documents every command.

On macOS and Linux:

curl -fsSL https://sean-reid.github.io/jamstream/install.sh | sh

The script:

  • Detects your platform, downloads the matching archive, and verifies its sha256 against SHA256SUMS.
  • Installs jamstream to /usr/local/bin when that is writable, otherwise to ~/.local/bin. Set JAMSTREAM_INSTALL_DIR to pick the directory yourself.
  • With -s -- --with-server, also installs the jamstreamd session server on Linux x86_64, which local mode with the CLI alone uses.
  • With -s -- --tag v0.2.0, installs that release instead of the newest one.

Uninstalling is the same shape:

curl -fsSL https://sean-reid.github.io/jamstream/uninstall.sh | sh

It removes what install.sh installed and nothing else. A session still running makes it stop and say so, since the binary being removed is what ends sessions; session records are kept unless you pass --purge, and credentials stay in your OS keychain either way.

On Windows:

powershell -ExecutionPolicy Bypass -c "irm https://sean-reid.github.io/jamstream/install.ps1 | iex"

The script installs to %LOCALAPPDATA%\Programs\jamstream (set JAMSTREAM_INSTALL_DIR to pick the directory yourself) and adds that directory to your user Path; open a new terminal to pick it up.

Flags need the script saved first, because iex cannot pass them:

irm https://sean-reid.github.io/jamstream/install.ps1 -OutFile install.ps1
powershell -ExecutionPolicy Bypass -File .\install.ps1 -WithApp

-WithApp installs the desktop app beside the CLI. -Tag v0.2.0 installs that release instead of the newest one.

Uninstalling on Windows is the same shape:

powershell -ExecutionPolicy Bypass -c "irm https://sean-reid.github.io/jamstream/uninstall.ps1 | iex"

It removes the binaries install.ps1 put in place and nothing else. A session still running makes it stop and say so. Your session records and local recordings are kept unless you pass -Purge (saved-script form again), which deletes both; credentials stay in Credential Manager either way.

If you installed by extracting a zip yourself, there is nothing to run: delete the extracted folder. Session data lives at %LOCALAPPDATA%\jamstream, and saved credentials are in Windows Credential Manager; search for jamstream there to remove them.